If your developer tooling is putting out #HTML that looks like this; I don't care what advantages that tooling seems to give to you the developer - the output is garbage that does not work with the grain of the web itself.
It's using the core technologies of the web in a manner entirely antithetical to their design.
It is anti-web.
This is a cul-de-sac of development practice.
@mattwilcox Every dev should have a look at their output and if looks like this - be ashamed. Unfortunately - mainly young - devs don't look at the source code anymore. #sigh
@hirsebirse I can't blame the young-uns.
Unfortunately this sort of tooling seems to me to be the result of engineers solving genuine problems, but engineers who have historically maligned HTML because "HTML is not a real language" and dismissed CSS because it simply doesn't work in the way that other programming paradigms do.
As a result, their ignorance has produced a little ecosystem of crap, that got big enough to sustain itself, for a while.
Can't wait to see it die out.
One apprentice told me this: "You're young. You want to do 'something with Interent'. You've seen a pal working on a page. So what do you do? Search for 'Creating web pages' and you'll find 'React'. So you watch a video. And what you don't get, is the fact that they teach you a tool. With DIVs. So you assume the web consists of DIVs". The rest is history.
That's why I teach my apprentices proper HTML and good old CSS. At first they don't see why - but in the end they thank me.
What's the point of using React if you don't know HTML? React main feature is generate and maintain HTML structures you define tag by tag. React is of no use if you don't already know JS and HTML.
