I'm not saying text content doesn't have its place, but what I am saying is that unless you're absolutely certain your users aren't going to be using JS (hint: that's effectively no one) then it's just not worth your time to accommodate those users - especially when they optionally disable JS, AND you have to degrade the experience for the rest of your users in most practical applications. How often do you design features for 1% of your users?
>AND you have to degrade the experience for the rest of your users in most practical applications
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.
A lot of it is about performance, if you need JS to fetch the content of your site after the SPA or Shell has loaded then you are incurring a significant amount of overhead for something that could have been streamed from the server and rendered as it was parsed by the browser.
Performance will come as the need develops. Yes it's faster to render something on the server right now, but that may not be the case in the near future. The concept of loading something from the server is also only accounting for a very specific use case. These days most websites will require more data from the server after the webpage has been loaded anyway.
Server rendering simply wont make sense for some binary applications, such as games.
Re:Regressive Web Apps
by robin_reala on Friday May 27, 2016 @08:18AM
(#11785484)
Playstation Now exists and is server rendering for games: https://en.wikipedia.org/wiki/PlayStation_Now
Re:Regressive Web Apps
by robin_reala on Thursday May 26, 2016 @05:33AM
(#11776686)
All the time, as 1.2% of my monthly users is 1.15 million people (hint: that’s effectively a lot of people). People will be accessing my content and using my services with Javascript deliberately off or situationally unavailable, and they need to be able to do so. It’s defensive design.
Re:Regressive Web Apps
by alistproducer2 on Wednesday May 25, 2016 @08:24PM
(#11774252)
From my experience having JS turned off, most sites render the text I want to read in a readable fashion sans JS.
Re:Regressive Web Apps
by perseusprime11 on Wednesday May 25, 2016 @06:23PM
(#11773623)
Is it really true you don't need JS for AMP? Checkout Washingtonpost.com/pwa
Re:Regressive Web Apps
by alistproducer2 on Wednesday May 25, 2016 @08:22PM
(#11774244)
AMP pages can’t include any author-written JavaScript. Instead of using JavaScript, interactive page features are handled in custom AMP elements. The custom AMP elements may have JavaScript under the hood, but they’re carefully designed to make sure they don’t cause performance degradation.
https://www.ampproject.org/docs/get_started/technical_overvi...
Re:Regressive Web Apps
by perseusprime11 on Wednesday May 25, 2016 @10:11PM
(#11774745)
Thanks for sharing. How do you go about taking a current website and building a PWA? Do I have to change my website architecture drastically?
Re:Regressive Web Apps
by angry-hacker on Thursday May 26, 2016 @05:24AM
(#11776660)
I'm interested what if my site already is 'amp' - do I really need to have a duplicate page? And add even more markup?
I don't understand amp, Google already has loading time as signal, just increase it even more.
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.