I'm not sure what drives developers to be so insular with thought and make so many assumptions about others. It seems like basic gate-keeping activity, but maybe it's just ignorance.
You don't get to this size because it's so hard. People aren't joining JS for the relatively low prestige, they aren't joining because the paycheck compares any better to any other part of the industry, and they aren't joining because of any promise of intellectual development — they're joining because it's the most accessible doorway in the tech community today.
There's no other part of the industry that's so clogged with amateurs trying to join.
The only other industry I can think of which is so hot in its community energy would be Python and ML, but they appeal with a different set of values. ML is hot because it's prestigious, ML is hot because the job market is insanely hot, ML is hot because it promises boundless intellectual exploration.
I just think that if you are saying so boldly that you don't need to use Javascript, then maybe your first example should be without Javascript?
FWIW I kind of feel like “no js” may be a pipe dream today. I see a lot of talk about it but very few sites actually do it; there just seems to be a lot of pressure to use the next big JS framework in the community.
Also analytics and so forth.
Jokes aside, it's a full stack framework, you need some server-side language. It's the served html that is (optionally) javascript-free.
Sure, not exactly "pure", but the point was basically to make it look like that.
https://dev.to/thormeier/dont-try-this-at-home-css-as-the-ba...
We already solved the CSS-as-a-backend problem. Too easy!
Jokes aside, this is every bit as unsurprising and dumb as I had hoped it would be. It's perfect.