You don't need a build system during development. I work on a 500.000 line web app, and it has no dev time build step. You check out the source into your web root, and run the app. Edit + f5 is fast enough, no need for smart build systems. Build steps are ofcourse inevitable for the jump into production.
The techempower benchmarks are open source. If you think it is badly written, send a pull request. Running your own benchmarks simply isn't feasible at the scale they're running them. We all benefit from a comprehensive and well executed benchmark suite.
I had this issue a few times, and each time it was due to an app being stuck on an initial setup screen. Going through the prompts solved it. Strangely I had the same issue on android a few times. My 920 gets two days of battery life.
I configured jshint inspection in a pre-commit hook on my team's code repository. Yesterday I checked the logs and in the last 10 days it prevented 15 commits, a few of which were actual bugs. For me static analysis is a no-brainer. The only challenge is finding the right set of settings that you don't get too many false positives.
On the other hand, it's a service to the user that old software keeps running. People who once invested in a copy of photoshop don't have to pay for upgrades they don't need. Or, in my case, i still use ecco pro to outline ideas, which saw its last update in 1997, is orphaned without source, and for which i've found no alternative that matches my exact flow.
I built a mobile web app that leveraged html 5 app cache so you could use it offline, and used metadata so that when put on the home screen it had a proper icon and when launched there was no browser chrome (on ios). It worked fine, and yet the guy who took over development ended up wrapping it. It made it easier to sell.
You're confusing server CPU usage with scalability and performance.
HTML template rendering on either the server or client is embarassingly parallel, as it just takes a viewmodel (basically) and populates a template of HTML with its variables, with zero other calls and dependencies.
You can scale this particular step to infinite number of servers, without any bottleneck appearing (hence, it's horizontally scalable).
And HTML template rendering on the server can be faster, because for client-side rendering you need at least two roundtrips to the server (fetch template, one; fetch content via JS, two), and for complex apps this becomes tens of HTTP requests (side panels, user context, footers, menus etc.), versus just one roundtrip for a server-based approach.
Request/response lag is critical in the way an app is perceived.
Also when it comes to CPU, as I already said in my previous response, view rendering is the cheapest step computationally you have in an app. Any other service takes more time and resources than that. So view rendering is never the bottleneck, and "optimizing" it away with complicated client-side shenanigans is the very definition of premature optimization.
"And HTML template rendering on the server can be faster, because for client-side rendering you need at least two roundtrips to the server (fetch template, one; fetch content via JS, two), and for complex apps this becomes tens of HTTP requests (side panels, user context, footers, menus etc.), versus just one roundtrip for a server-based approach."
The template fetch is only the first time.
"Request/response lag is critical in the way an app is perceived."
Yes it is and it is worse with server rendered pages.
A typical size of a page fully dynamically generated on the server side could be a few times larger than that fetching of data/content.
The token is returned by the auth service when the user logs in. The initial page bootstraps in unauthenticated mode and always has to query the auth service first to figure out if the user is logged in. That's how I've done it in the past.
This isn't unique to the US. In most countries the carrier restricts ota updates for android and windows phone. I don't know why the iphone is the only device which doesn't need carrier approval prior to rollout. I also don't know why the carriers are involved, but it's definitely not unique to the US, most of europe is the same way.