These are old complaints.
My dad worked in the tech industry since the pre-Mosaic days, and even then you'd hear the same arguments and complaints.
The same way people complain about React today is the same way people complained about Spring, and then about how old school C programmers complained about C++ with it "training wheels", and BASIC programmers complaining about "OOP", and old school networking types complaining about built-in TCP/IP instead of spinning up your own stack.
Technologies and frameworks change. That's how tech always works. Sure I can demolish a building with a sledgehammer, but why not adopt dynamite or bulldozers if it efficiently solves the problem.
At some point, all these complaints are just Ludditism from techies who didn't upskill and/or are unable to communicate.
Us older heads know how often it goes wrong, and know that without a tangible user benefit or commercially positive outcome... It's just busy work.
Oh you are going to rewrite established solution X in Y in 2 years with 5 devs, and it's going to solve all of the problems we have in X, awesome!
Ignoring that solution Y is so new that the guy proposing it has never actually delivered an enterprise solution in it. And since they just got hired, they have no idea what the user facing problems X is actually exhibiting. Often the problems with X are organizational, managerial, and prioritizing. Switching tech doesn't magically change the decision makers.
Invariably hiring a guy who has a string of 18-24 month jobs on his resume, which, uncannily, is the typical runway of a Greenfield re-write project before heads roll.
Not every tech is the new Spring, OOP, etc.
Not every project benefits from being immediately migrated to the new thing.
Once you've been through a few train wreck "get on the latest thing" projects, you see the benefit of actually delivering to users, regardless of whether the tech is bleeding or trailing edge.
If you are a small tech org, the benefit of being able to hire a team of people who have SUCCESSFULLY delivered with TechX (which is 3-10 years old) can outweigh jumping onto the latest thing.
I think the problem here is the usual bloat and enshitification that these tools eventually devolve to due to their success. People get so used to them they want to use them for everything and create this universe where you now forgot why they were created and the places they were useful.
But what about all the mis-adopted or abandoned tech that blew up projects.
The amount of stuff ported to NoSQL that had no business doing so. UML/Nocode tools in the 90s.
A lot of the push away from Java only for a lot of performance considerations pushing devs back to it. Sorry about the projects that got force migrated to Scala since it was, briefly, The New Thing.
The one man webdev app deployed firmwide on some brand new framework which was immediately deprecated.
Again, nothing wrong with any of these tech choices if they were driven by actual user requirements which exceeded the current implementation tech. But most of us know that is rarely the actual motivation of devs...
MongoDB easy (in a way) replication put every single database vendor on watch and led even PostgreSQL to improve, i think we live in a different environment right now due to all the experiments the NoSQL folks made. It might not have all panned out but I think the whole thing was a huge positive for the market, people stated to experiment and try new stuff again instead of "oh it doesn't look like a relational model, it sucks".
The amount of "how do I justify a rewrite because our tech stack is bad" posts you see in your typical reddit/etc programmer forum would remind you of this.