I don't think the trend of heavy SPAs will go away, but browsers could do better by sending a header/status code to indicate JS is disabled. Preferably as part of a future enhancement of the HTTP standard.

This would allow for much better tracking of who actually disables JS. Yes, tracking, but actually beneficial in this case. I'd imagine it would be a lot easier to make a business case for a limited version akin to for a lot of devs if armed with hard numbers.

On the other hand, it may also be just another datapoint for fingerprinting. However, there's so many of these already, that the benefits probably outweigh the cons here.

Show thread
Sign in to participate in the conversation
Matej Lach's mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!