Comment by mvdtnz
4 days ago
A truly overwhelming majority of users browse with JS enabled. Designing or even considering those who don't is (in the most literal way possible) a waste of time.
4 days ago
A truly overwhelming majority of users browse with JS enabled. Designing or even considering those who don't is (in the most literal way possible) a waste of time.
No, because this is about more than just supporting non-js use cases, it is about the type of design from the ground up and how you structure your application. JS is very welcome on these kind of interfaces, but also really unnecessary for what it actually does. It just adds bells and whistles. Or it should "add", if designed correctly. As another comment pointed out, now it takes more network round trips and uses more ressources. And now it does not work without JS anymore.
A good designed web app works just with plain html and minimal ressource use and than adds on top of that the get even better with css and js niceties. This used to be called progressive enhancement, if the client supports a feature, make your website better for these clients. It's just better and well rounded design with the added bonus of supporting clients with less capabilities.
Yea to be concerned about a product’s direction on account of not pandering to the 0.0001% of users is hilarious