[robin_reala]

I built a side project a couple of months ago[1] that’s a PWA-installable interactive experience, but also degrades down to styled information in the absence of JS, and back to raw HTML if CSS fails. It’s surprisingly fun to build in this way.

(On another note, choosing to avoid a framework and just use some vanilla JS led to an extremely fast loading site.)

[1] https://www.designcritiquecards.com/

[dariosalvi78]

congratulations, but how many people have the time to do that? Is it really feasible on big projects?

[robin_reala]

Depends what you’re doing. The majority of the site I work on for my day job is statically rendered and theoretically works without JS, but large parts (including any ecom functionality and profiles) fail. Would it be worth making them more reliable by falling back if JS fails? Possibly, but that’s difficult sometimes to argue for in today’s environment of features-first from product, and developer-experience-first from engineering. Still worth the effort.

By the way, we are talking about reliability-in-depth here rather than user choice. I wrote a blog post about this a few years ago: https://www.robinwhittleton.com/2016/09/19/why-we-use-progre...