I see a lot of complaints that employers want X years of experience in a framework that has been out only X years or even less than X years. Also see complaint

I see a lot of complaints that employers want X years of experience in a framework that has been out only X years or even less than X years. Also see complaints about having to keep up with too many new frameworks/libraries etc. Hopefully both good developers and good employers/clients will realize that frameworks are like cars. You might be a mechanic who specializes in Corvettes but that doesn't mean you can't change the tires, do the brakes, or diagnose the oxygen sensor on a another make or model. The really valuable skills, in developers or mechanics are knowing your tools and how to choose the best one for the job, knowing the diagnostic/troubleshooting process and knowing the underlying systems that make a program/vehicle run. Sure there will be little gotchas or time-savers that a specialist will have developed but those are usually mitigated by joining a team that can point them out to you or just by working with the new framework/library for a while. They certainly don't prevent you from being productive.