Hey hey, easy there! You should work in your anger management! Or maybe that's just a character, to get more followers, well... it is the Internet so it should work I guess.

Anyway, I have even updated my article with a comment, because it has attracted the wrong kind of attention. This one is not focusing on HTML and CSS at all, but rather on possible approaches that wouldn't use them because, whether you want it or not, developers use these extremely successful and opinionated JS frameworks (that I don't necessarily like) as they are demanding something else.

If that's right or not, this is not the point of the article. As I said to other commenters that also thought I hated the current stack (which is false), this is less about opinion and more of a reporting. In the end, I don't even think that HTML and CSS are going to be replaced by anything anytime soon, as I stated there. One of the points I mention in the article is that any technology meant to replace HTML and CSS will have to do all the things that are done by those, which is far from being simple and straightforward.

This article does not go into why HTML exists and why it is used or why it is like this, neither it goes into separation of concerns or HTML semanticity, and it goes into accessibility mentioning it as one of the problems to be solved by a proposal to replace the whole FE stack, should one ever come. In fact, there are already "early bird" developers using those tools today, which is wrong mostly because they are ignoring accessibility completely. I personally don't want that, so I'm pinpointing this one as the main issue. Please make sure you have read the article next time, also note that I may not be that different from you in my intentions and preferences at the end.