Just as a nice case study...
I was "old" when SOAP got popular (late twenties early thirties). Most of my (age) peer group seemed to agree with me in that it seemed over complicated and messy. We were, of course, old stick-in-the-muds who couldn't adapt to the new technology :-)
It was the "young" developers who jumped on it more than anybody else that I saw - the everything-in-xml crowd.
Ten years on, of course, the "young" crowd are now seen as "old".
Plus ça change, plus c'est la même chose :-)
Ageism cuts both ways, and it's never an excuse for winning an argument or evaluating a person. You evaluate people on their merits or you pass over valuable people and pay the price for it.
Amen. Young and old both have stick-in-the-mud types. It's just that the young folk haven't had the time to demonstrate whether they are stick-in-the-mud types. You don't want to hire them whatever their age.
Using node.js (or whatever) doesn't make you cool, hip, and open to new ideas. I can guarantee that, if this forum is still around in ten years time, there will be somebody complaining about this old fker who wants to do everything in node.js :-)
In the same way (not industry-related) I've observed that people who are 50+ years are seen as "elderly". That was 60 or 65 some 15 years ago.
All other things being equal, I'll always pick the older engineer with more experience and maturity than the young engineer without.
Ageism cuts both ways, and it's never an excuse for winning an argument or evaluating a person. You evaluate people on their merits or you pass over valuable people and pay the price for it.
Older people can be full of hubris too, using appeals to experience and authority arguments to shortcut rational thinking.
Using the I'm more experienced than you argument is the same as people saying you insist on C++ cause that is what your comfortable and experienced with, and you'll cost the company millions in lost productivity.