News for hackers. Stuff that matters.
Re:JavaScript Fatigue by chubot on Monday December 28, 2015 @02:38AM (#10800292)
I'm not really buying it... Rendering on the server seems like a solved problem to me. Web apps scale.

Sure, you can save servers by offloading work on the client. But I think your server cost is absolutely dwarfed by developer salaries. I guess it depends on whether you have more front end people or back end people. Good front end people seem to be just as expensive and rare as good backend/C++/Unix/distributed systems people these days.

On mobile, most web apps are a disaster. They are certainly a lot worse than light HTML. Never mind waiting for the server on every action -- try getting the app to load in the first place! The Android and Chrome team have numbers on the astronomical rate of user-aborted or otherwise failed page loads on mobile. On mobile, users see the white screen for 5-10 seconds (probably waiting for your 10-50 round trips for your JS, CSS, heavy image assets, and especially third party JS) and then give up.

Re:JavaScript Fatigue by frik on Monday December 28, 2015 @03:52AM (#10800432)
You are so right!

I hand tuned web apps (vanilla JS5, no libs/frameworks) and opimized them for mobile, and they are very fast.

But most don't care and use bloated JS libraries/frameworks and the end user has to wait several seconds until the 1MB JS file loads over a cell connection or even crash the mobile browser because the site owner thought it is okay to integrate 30 advertisement and analytics third party JS files.