Explore >> Select a destination
|
You are here 
|
blog.codeminer42.com | ||
| | | | |
www.carloscaballero.io
|
|
| | | | | Thoughts, stories and ideas. | |
| | | | |
cathydutton.co.uk
|
|
| | | | | Following on from Surviving CSS, CSS layers looks at layers of responsibility in CSS.} | |
| | | | |
www.hongkiat.com
|
|
| | | | | There's a handful of great methods for structuring CSS code, and they all work in different ways. The most popular ones are OOCSS and SMACSS, but there's | |
| | | | |
blog.owulveryck.info
|
|
| | | This article explores the transition from a WebSocket-based implementation to a simpler, more direct stream over HTTP in the context of capturing touch screen inputs on Linux. It begins by introducing the main theme, encapsulated in the statement Everything is a file is a stream of byte. The need to capture finger positions on a touchscreen by reading /dev/input/events in Linux is initially discussed, followed by a dilemma of transferring this data to a JavaScript client in a browser. Initially, WebSockets are chosen, leading to a discussion on how frameworks often shape our technological choices and the challenges faced in debugging WebSocket connections. The article then introduces an alternative about sending a stream of bytes over HTTP, drawing a parallel to Linux's approach to handling devices and files. Serialization, the process of encoding messages for this stream, is discussed next, highlighting the implementation specifics in GoLang and its native advantages. The final section covers how to receive and decode this stream in JavaScript within a worker thread, and then send the decoded messages to the main thread using post requests. The article concludes by reflecting on the benefits of simplicity in technology, urging readers to reevaluate default choices and consider more straightforward solutions to complex problems. | ||
