But the tides are already turning and more and more web developers are starting to understand that the whole Node thing was a big mistake. Look out for Elixir based sites pushing server rendered content over websockets.
-
This is completely backwards. The point of a distributed system is to distribute work so the cost isn’t concentrated unrealistically in a central point. And you want the visuals generated on the client so they can be maximally responsive at e.g. 120Hz with subtle color changes
over time and so forth. Yes it’s not a good idea to have the browser be an OS with JS and HTML the systems languages. But removing those solves the problem, and this is easy to see for anyone who understands performance. Your proposed solution is anti-performance and
-
-
anti-quality ... in your world running a web site is tremendously expensive and still sucks for people on low-bandwidth connections because it takes a long time and a lot of bandwidth to load anything by and I guess they get blurry text or something?
-
None of this is necessary. We can cut operating costs tremendously from what they are today, and have clients run at much higher performance, and it would be very very easy actually.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.