Heh, someone at work is adding a new JS framework to something to do something that is likely quite doable without it. Again.
But what can I really do? I gently suggested that it might not be necessary, and that's pretty much all I can do. It's not in a product I work on directly (although in the future, I could end up on it), and adding frameworks to solve every problem is so firmly normalized now, that you kind of sound like some know-it-all if you suggest that you can do things without them.
This comes right on the heels of a post yesterday on a message board talking about replacing an "outdated" VB6 app that walked users through some options, then generated a text file. The non-cranky sounding consensus leaned toward Electron, which is basically shipping an entire browser to generate a text file in a "nice" way.
To put things in perspective, though, "slap something someone else wrote on it; it's more standard" syndrome is not even in the top three worst things about working in software now. That kind of wastefulness is dwarfed by applying LLMs to anything and everything as well as companies just being blatantly shitty house flipping operations completely divorced from making things that help more than harm.