There is a tendency for a lot of people to hang on to tools and ideas that worked for them in the past. e.g someone who comes from a relational world, finds it very hard to get used to nosql unless their boss gives them no choice.
"Reactive", "Streams", "Containers", "NoSQL", "Big Data", "Blockchain", the list goes on. I work, or have recently worked, in each of those problem domains to a non-trivial extent, so I'm absolutely no stranger to the leading edge of the marketplace, but I still find it amusing how gaga people get over the new branding, and I'm even more amused how indignant people get when you show them work from 15-20 years ago that was materially similar under the "hot new" brand name it had back then.
Sure the show might be new to a lot of people, but to a lot of other people it's just re-runs that have been in syndication for a long time with tired plot devices and predictable story arcs.
Reluctance to jump on the bandwagon may very well be rooted in the scar tissue built up the last time around, not purely reticence to try something new. They may just be withholding their enthusiasm until they try can something actually new.
Also what is the analogue to reactive in the past ? The main reason for reactive is different screen sizes and orientation of handheld devices. What similar problem would reactive have solved 2 decades ago ? There are a couple of references from 2001 and 2004 https://en.m.wikipedia.org/wiki/Responsive_web_design , but really there wasn't a practical common use case before the iPhone in 2007 and ipad in 2010.
I work on a system at my dayjob that was "NoSQL" in the 1980s and is functionally similar to modern document-databases.
So...yeah. I'm sorry but the idea these things are "new" is the perception of someone who hasn't touched older technologies.
It might be that I am beyond redemption at this point.
I'm in my 20s and I've said this comment before plenty but it isn't in the context of someone being too old to ship code but instead the fact that as we age we usually take on additional commitments, responsibilities, etc.
All these extra factors often limit the amount of time that most people have to dedicate to coding.
I'm in my 30s and have what you call "more responsibilities" and can tell you that I now value my time more, get more s--t done in less time and overall are more productive than in my 20s when I had none of those responsibilities.
BTW, since somebody's likely to ask, I'm 51.
