What is the point of this sort of lowbrow sarcasm, fueled by raw cynicism?
Web applications have gotten significantly more complex. From a developer perspective, managing resources separately is a lot easier than using image sprites, giant merged CSS files, etc, though such is often forced because of the known inefficiencies of HTTP. Yes, this seems like an improvement. Are there sites that have other problems? Yeah, sure, of course. That doesn't make it less of a benefit.
Maybe the problem isn't that trucks are too slow, maybe the problem is that you're shipping too much crap, like JavaScript frameworks that reimplement loading a page. Oh the horror of letting the browser load pages!
The point is that the modern web is an abomination. The web isn't for applications, it's for documents, but web developers refuse to acknowledge this, so they do everything in their power to circumvent how the web works (or should work) to avoid making a native application.
The world would be much better served by plain, unrendered Markdown documents (or something similar) served statically by an FTP server and rendered appropriately by the client. No JavaScript, no CSS! Just a document. In cases where this is insufficient, build something appropriate to deal with it.
Okay, so you have a strong opinion in a field that you are opposed to. I think that can pretty soundly be discounted by anyone who cares about this industry.
I care deeply about the Internet, and about the web, and I think that the widespread prevalence of JavaScript-only sites is a plague. Users should not be forced to execute code in order to read text. In a way, JavaScript is equivalent to DRM: it's an unnecessary hoop.
>Users should not be forced to execute code in order to read text.
Yes, because who on earth would like interactivity on their site? Can you imagine it! Not having to reload the entire page on every little interaction! Blasphemy!.... /s
Who on earth would want the subjective experience of reading a page to subject him to executing untrusted code, potentially compromising his privacy and security?
I'd love it if all browsers had an 'Enable code' button or somesuch which had to be manually clicked for every page which used JavaScript. And not remembered. That'd go a long way to ensuring that JavaScript were only used where necessary.
(for that matter, books have managed to be quite remarkable for centuries, with absolutely no interactivity)
What is the point of this sort of lowbrow sarcasm, fueled by raw cynicism?
Web applications have gotten significantly more complex. From a developer perspective, managing resources separately is a lot easier than using image sprites, giant merged CSS files, etc, though such is often forced because of the known inefficiencies of HTTP. Yes, this seems like an improvement. Are there sites that have other problems? Yeah, sure, of course. That doesn't make it less of a benefit.