frezik

Maybe we could have No-JS and No-Client-Storage (which would include cookies) headers added to HTTP. Browsers could potentially display an icon showing this to users on the address bar.

Theoretically, browsers could even stop from the JS engine from being started for the site in the first place. Though I wouldn't be surprised if the engine is too tied into the code of modern browsers for that to work.

Let's not. It's a terrible protocol with amateur design errors.

JS does a lot of crap that didn't need doing in the first place. It can be used in a way that improves performance and user experience, but what's out there is so far from that.

HTML could maybe be replaced by a specific form of Markdown (one with a real spec), but meh, whatever. Gemini did that, but its limitations are a little too much.

Was never part of the standard.

You want to do what Gemini did. Take Markdown, add some specific features to make up for some blind spots in the original, formalize it, and give your version a specific name.

Someone will thank you for your service. Not me, but someone.

Which is important because about a year ago the headlines were saying EV sales were collapsing. In fact, it was just Tesla having less market share of new EVs sold because other manufacturers got off their ass.