And they purposely hobbled certain things people want, like inline links and images. Some clients will do it anyway, but it's against the collective wishes of the developers.
If I wanted to track people on Gemini, I could totally do it. It'd just be in a more server-to-server way than how its evolved on HTTP (pixel trackers and such).
Some people haven't lived through the time when HTML layout was done through nested tables, and it shows.
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.
Since 1970, productivity has increased by 86%. That suggests the output of a 40 hour work week in 1970 could be done in under 22 hours with the same inflation-adjusted wage. That's not even considering the productivity increases caused by industrialization in the century before 1970 (though the 40 hour work week in the US wasn't set until 1938).
Admittedly, this is a bit of a naive way of looking at the numbers, but it gives ballpark ideas of how far we might be able to go.
Note that real (inflation-adjusted) pay has only increased 32% in the same time period. This, BTW, is a much more robust argument than saying real pay has flatlined since 1970. Real wages are, in fact, up during that time period, but it's possible the numbers will shift again over time and return to being flat or down. The pay-productivity gap, however, has only been widening with time and isn't going to be fixed without drastic changes in policy.
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.
Because they are cowards.
It depends on the city. Mine (Madison, WI) doesn't officially list any party affiliation for mayor or city alders. We also use a runoff election system, so we're not stuck on two parties for local things.
In practice, candidates are often backed and/or endorsed by some political parties. Common ones are Progressive Dane (county level party) or Working Families (which has national reach and is basically a socialist party working within the Democratic party). When they move up to state or federal seats, they usually join the Democrats while continuing to work with the Working Families party.
There are ways they can work around it, but their lead developer was drafted into their country's military. Ultimately, they're going to have to make their own phone, and it looks like they're making plans to do that.
For now, it's fine.