From the perspective of a web developer or publisher, they of course want as much power as possible. But this is really a tradeoff, directly taking away power from end users - the accessibility you handwaved away, as well as things like adblocking, user-styling, caching, and every other unenumerable concern of endpoints.
I'm not saying that a delivery system for opaque executable blobs isn't the inevitable fate of the web, just that this shouldn't be viewed as progress but rather decay.
You are speaking of things that can and should be addressed with APIs provided by the browser.
For the former, then the browser still needs to be able to understand the page to implement this API functionality. Turing-completeness is incompatible with this understanding.
For the latter, then that requires page authors to explicitly opt-in to those mechanisms. Obviously they won't do this when incentives are opposed (eg ad blocking). And even in the cooperative case, would require pages to anticipate all features viewers would require.
Why do you think Google created AMP (which is just a fancy way of telling devs to stop using JS for text sites)?
Look, there are plenty of site for which JS makes a huge difference - proper web applications. For every one of those site there are 9 that load half a MB of cruft so they can animate their stupid banner.
I would say the opposite. The absolute majority of developers who insist on requiring JavaScript with no option to gracefully downgrade on pages that do not need it are the ones degrading the web experience.
Server rendering simply wont make sense for some binary applications, such as games.
https://www.ampproject.org/docs/get_started/technical_overvi...
I don't understand amp, Google already has loading time as signal, just increase it even more.
It's not that nothing should change, it's that change should make things better. I firmly believe pages made better by javascript are such a small minority as to be an rare exception, but overall the web is so much better with that 'feature' disabled.
I don't understand your reasoning; I don't have any HDMI equipment (except my RaspberryPis, which are headless servers anyway), so I certainly would avoid anything that's HDMI-only.
Just because you, at the moment, only use the Web for a few pre-approved purposes (e.g. viewing rendered pages) via the handful of user agents which support Javascript, on operating systems supported by those user agents, on hardware supported by those operating systems, which is powerful enough to run it all, that doesn't mean everyone else is. Some are less fortunate, as they have older, or less-powerful equipment. Some are more fortunate, as they are using the Web in more imaginative and novel ways than you are.
Web pages can be rendered any which way you please, it's no skin off a developer's back if you don't have JS enabled for their JS project.
I don't specifically avoid HDMI, I've just never encountered a situation which involved HDMI. Also, I hear it's riddled with DRM, and I don't see the point upgrading when it seems to be becoming obsolete anyway (DisplayPort? ThunderBolt? Newer USBs? etc.)
- Hideous wastefulness of resources, causing constant unnecessary repaints, enormous RAM usage, etc
- “Experiencejacking”: things like scroll hijacking, back button hijacking, etc
- All the privacy invasions that JS enables
These wouldn’t be issues if sites suffering from them were the minority, but they’re not. Most sites have mountains of poorly optimized JavaScript that gives zero thought to performance or resource consumption. Once it works, it’s shipped.
The fact is that front end web dev culture as a whole places very little value in things like performance, battery life, resources, and ultimately, respect of the end user’s desires, and that’s a huge problem. As long as the whizz-bang shiny flashy checkboxes are checked, it’s all good.
To borrow your comparison, people who are bothered by what I describe above see it like a website saying, "Hey, we won't work on your device unless it's HDMI because of the design choices we made!"
What is so bad about JS that you just can't use the web with it enabled? Grow up.
The web is a platform that is evolving far beyond its original intent. In a few years its going to be a binary delivery platform. And that's great news. The idea that the web needs to stay the way it was designed in the 90s is what's really regressive.
Here's what matters about the web:
- Linking
- Standards for Web APIs
- Content delivery protocols
Everything else - as far as I'm concerned - is a transient feature which will eventually be superseded.
The mentality that nothing should change about the web is incomprehensible to me. I just don't get it.
Edit: Inevitably, someone will tell me that the web is faster without JS, and another might claim accessibility as a problem.
- A faster web is made possible by faster devices on faster networks. Current constraints are far less relevant when we're discussing future technology. For now, yes page size is a problem but I absolutely wouldn't want that to shape future technology. ISPs have the power to improve their services as required.
- Accessibility is a standards problem, not a content type problem. Accessibility software should be expected to adapt to new technology like anything else. As long as we provide the tools for these platforms to succeed, the type of content that is being served (whether it's plain text, JS, or binary) shouldn't affect anything.