4 ms·
My personal discoveries: * Websockets + JSON is 8x faster than HTTP and less error prone, so I worked on HTTP elimination in my app to great success. It has al
by austin-cheney 4y ago
My personal discoveries:
* Websockets + JSON is 8x faster than HTTP and less error prone, so I worked on HTTP elimination in my app to great success. It has all the advantages of gRPC but you don’t have to deal with protobuf.
* Browser performance. My OS GUI loads in 200ms on Chrome and 300ms on Edge with full state restoration, which is faster than the GPU can visually render the output to screen. The performance tab in the browser dev tools is amazing.
* When you have a solid foundation you can scale an application in any direction very quickly. In the browser I am working directly to the DOM and treating it no differently than the file system: a big giant globally available living tree model. In the past week I wrote a command terminal that works in the browser with autocomplete and ANSI color support and it took about 10-12 hours because the application is mature.
* I see many new developers struggle with async functions and promise chains. I made a commitment to myself to avoid such struggles and fallback to old style callbacks which are more verbose and less clever.
- Existenceblinks 4y ago> Websockets + JSON This is the way. Phoenix Channel is my best friend. > Browser performance Yeah, they are definitely improving. Firefox got a huge bump memory improvement recently. Chrome renderer is slower than Firefox though in heavy nodes scenario. Safari .. hmm sure lightweight but also light features. > old style callbacks which are more verbose and less clever Those who are familiar with functional style like this way better. It flows through which is nicer than holding the promise with name for avoiding chaining sake.