In your argument, you could replace HTML/CSS with Assembler and JS/React/whatever with C and everything that came after.
The productivity gained from these Tools is worth it, even if some use cases could be solved without it.
The productivity gained from these Tools is worth it, even if some use cases could be solved without it.
So much content is published in Github READMEs (typically markdown) and while Github itself will have Javascript elements, it does demonstrate that you don't need Javascript heavy sites to publish content.
I honestly think half the time the front end best practices are based around what's more intellectually interesting for developers rather than what is genuinely a better website.
What you get? Routing, instant refresh, image optimization, and code optimization (your CSS could be smaller if you minify it).
You don't gain productivity using 500 libraries pulled off NPM unless it's write once read never.
The comparison was foolish then and just as foolish now.
You really are an extreme case of the dunning kruger effect in action.
I don't think you know what Dunning Kruger is. I have never claimed to be anything great. I only mentioned I wrote an application and other people used (continue to use) it.
And I am surprised that I have to point it out again: that you once wrote something which people used in java script says nothing whatsoever about your experience in frontend development.
In fact, it kinda confirms that you don't have any.
You sound like a grouchy old man that got left behind and loudly complains about it.