Ecosystem-fatigue maybe? I don't know if there is an existing term for this but it's got more and more common and it's going to get a hell lot of more.
As a junior engineer (20+ years ago, for me), anything new is enjoyable. Damn we even enjoyed .NET, J2EE, Perl.. whatever crap. You name it. But today there are so many frameworks, paradigms, tools, services... and sad thing is in many cases the differences are nuance-grade which for senior engineers might become incredibly exhausting, at least in my opinion. "Why would I want to spend 6 months learning Vue if I can do this in React in 6 weeks?", "Why should I learn Rust if I just can do this in C++?"...
I think there are big differences in how industry evolved in the early twenties to today. I think today's evolution can feel rather disappointing.
As a junior engineer (20+ years ago, for me), anything new is enjoyable. Damn we even enjoyed .NET, J2EE, Perl.. whatever crap. You name it. But today there are so many frameworks, paradigms, tools, services... and sad thing is in many cases the differences are nuance-grade which for senior engineers might become incredibly exhausting, at least in my opinion. "Why would I want to spend 6 months learning Vue if I can do this in React in 6 weeks?", "Why should I learn Rust if I just can do this in C++?"...
I think there are big differences in how industry evolved in the early twenties to today. I think today's evolution can feel rather disappointing.