Amen to this. I went to college in the late 90s and was blown away by the people who saw a CS degree as a good way to make money without having any actual interest in the field. They spent four years bitching about not getting trained on the flavor of the week technology because they couldn't extrapolate how things they learned in language A could be applied to language B with minimal work. Those of us who actually wanted to know *how* things worked and what was underlying whatever keyword / checkbox was "critical" on a resume have done pretty well but I would be shocked if half of the people who went into it for a quick paycheck were still in the industry.
The giant tech bubble bursting about the time I graduated played a roll in sending me to grad school but it was a hell of a filter on the somewhat capable, get rich quick students.
When it comes to hiring, I don't care how old you are. In fact, I'd rather have the less frazzled older guy working 40 hours a week than the guy fresh out of school working 60 but producing 30 because he's going back and fighting his own design decisions every other day. Keep updating your skills. If that new language or framework really looks promising, great, do some side or personal project in it. Be prepared to explain why the new is or isn't better than the old. Don't blindly embrace the new and don't blindly hold onto the old just because you know it. Show me you can use your brain since that's kind of a requirement for these sorts of jobs. Too many people couldn't debug their way out of a paper bag. Try not to limit yourself based on your prejudices. I'll never love working in javascript, but I know I need to be competent. Don't try and bluff your way through talking about something you know literally nothing about. I'd rather hear "I know the name but I've never worked with it" than watch you make an ass of yourself explaining something I understand and you googled in the waiting area. If you're enthusiastic, bright, clearly know what you're doing with at least tangential skills, and demonstrate that you can pick up new things then I can overlook some mismatch of training. I mean, come on, if you're *really* good at almost any procedural language you'll have 90% of what's required in most of the rest. These are not all special and unique snowflakes. Show me you can *think*.
Ugh, sorry, had some flashbacks to days interviewing new hires.