Your point stands and is about as real as the idea of millenial hipsters saying "Oh, sure, we have a jQuery app that works right now, but that's so 2010, if you

Your point stands and is about as real as the idea of millenial hipsters saying "Oh, sure, we have a jQuery app that works right now, but that's so 2010, if you don't have an SPA everyone is laughing at you and if you think you're going to write an SPA with just jQuery do you even code bra, let's spend 6 months converting Angreactive, it's the modern-iest framework out there!" Which is to say, sure, you can boil people down to caricatures, and there will even be people who match them. There are reflexively recalcitrant developers who don't want to adopt anything new, there are technological magpies whose decisions are driven by fashion and resume bullet points. The former probably do tend older, as they have a sense of less time in general and would prefer to reserve learning for new capabilities rather than different ways of doing the same thing, and perhaps even be judicious about time learning vs doing things they value. The latter probably do skew younger, as it's easier to feel you have years and energy to burn and less reference for how change works in the industry. So what's very real are the incentives and tradeoffs underlying the decision making. The idea that what the past has provided is often adequate and investment in the new has costs is correct. The idea that there may be improvements in the new is also correct. If you believe this, maybe having cranky 50 year olds who are going to make your organization justify its decisions is actually an asset along with people who are curious to invest in the new shiny...