Lets be clear not everything needs to work without JS for a project to be a progressive enhancement success.
The feed on GitHub might have been deemed non-essential.
Sure, I was totally teasing :-)
There should be better ways to handle than turning off features, but how do you get a dynamic feed without JS? You don't. Technically you could iframe it, or queue it for generation, use a refresh header, but then you risk interrupting other user behaviours.
You can probably simply render the last 10 items of activity in HTML and that's it.
This is how the page looks without JS:
I don't have answers. I don't work for major browsers. I'm glad that large orgs are looking to avoid unnecessary JS, but it'll be a while before it can deliver native application experience, or sadly dated application experience without scripting.
I feel like we're on different points on this. The purpose of progressive enhancement is not to give users the same exact experience, is to give users a functional experience. I can use GitHub without JS but I know I lose comment previews and stuff like that. The website goal is still 100% reached.
To use a search bar you don't need autocomplete and so on. Also why would you need service workers in a HTML + CSS web app?
I applaud your effort but I don't share the same goal.
The failure is when with JS turned off you get no website or a broken one.
I was reading an article (only images and text) on Vice Italy a few minutes ago, just for curiosity I tried to reload the article link with JS disabled and I got a blank page, with nothing on it. I have no idea what CMS they use but there's no reason in the world to have a magazine website to be completely broken without JS.
The point of progressive enhancement is to let me read the content and see the images even if I don't have flashy animations or preloading :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sure, I was totally teasing :-)
You can probably simply render the last 10 items of activity in HTML and that's it.
This is how the page looks without JS:
I feel like we're on different points on this. The purpose of progressive enhancement is not to give users the same exact experience, is to give users a functional experience. I can use GitHub without JS but I know I lose comment previews and stuff like that. The website goal is still 100% reached.
To use a search bar you don't need autocomplete and so on. Also why would you need service workers in a HTML + CSS web app?
I applaud your effort but I don't share the same goal.
The failure is when with JS turned off you get no website or a broken one.
I was reading an article (only images and text) on Vice Italy a few minutes ago, just for curiosity I tried to reload the article link with JS disabled and I got a blank page, with nothing on it. I have no idea what CMS they use but there's no reason in the world to have a magazine website to be completely broken without JS.
The point of progressive enhancement is to let me read the content and see the images even if I don't have flashy animations or preloading :D