Thanks for trying though. The fatigue is real.
It's not, both because it's incoherent English, and because it doesn't tell us what distinguishes this framework within the space of new frameworks.
> I think this is pretty much a step backwards towards in-page PHP or some XML logic parsing.
I'm not sure why programming code embedded in HTML is substantially worse than the reverse (e.g., JSX). We're mixing syntax and concerns either way.
Neither does "The main problem with all those frameworks is JavaScript".
In-page PHP is ugly, but it sure let normal people who had gotten comfortable with serving static HTML make dynamic web pages quickly. It's also highly performant.
PHP does after all have a straightforward mental model and expressive syntax, but now we have learned to build better (more secure, more resilient, performant, better architected, etc) web apps. IMO very worth a watch.
Why? Although I agree PHP itself is ugly, I always considered this particular part beautiful and alone worth tolerating the rest.
the fundamental premise still holds. we need to go back to roots and improve on HTML.
Oh, get over yourself. Whatever "fatigue" you are feeling is completely of your own choice. Other people aren't beholden to you for their desire to make things.
I cannot express strongly enough how much I hate comments like this. Go live in a utilitarian dystopia if you hate people making new things so much.
That said, it's pointless to comment about and I do share your sentiment that the equally as frequent echo of pessimism isn't worthwhile.
Choose your own adventure already.
You choose to look at things like this and feel fatigue. Nobody forced to to look at it. Nobody told you "that's it, start retaining now". You have a fundamental fear of missing out that, instead of addressing the fear and feeling secure in your own choices, you feel necessary to externalize as criticism towards people exercising their own free will.
React existing or not existing or being old or not being old is not a reason for others to not do the work they want to do.
As a consequence, there is a tiredness and skepticism about new things. It's not that people feel that it's necessary to retain, it's that people enjoy learning about new options, but find that their lived experience has given them a resistance to that which they might otherwise enjoy.
They approach new things with interest, but end up frustrated to find more of the same.
Also you can't just tell people to not feel things! That's not how emotions work!
No, they have not. Not any more than the rest of us. Not any more than any other profession.
I really think this whole thing is borne out of Code Camp graduates coming into the job market thinking all they needed was whatever minuscule collection of shell scripting incantations they learned in the Code Camp to get a "Zomg 6-figure++ salary". And if that is all the training you've had, I can easily see how it will feel like it is inadequate (because it is). But the answer is not "keep feeding the inadequate way of learning".
And it's certainly not replying to someone's thread in which they present their hard work with "uuuuugh, woe is meeee".
Here's an idea: listen to how people feel rather than tell them how they feel.
If people have felt the need to do something and so have done, that's as good as saying they needed to — if sufficiently done en masse. Whether that attitude was justified in the first place doesn't negate the fatigue they may now feel — a feeling they're more than entitled to, even with you saying they're not.