> What I’ve learnt through experience is that the number of languages I’ve learned or the specific frameworks I’ve gained experience with matters very little. What actually matters is my ability to up-skill quickly and effectively. My success so far has nothing to do with the fact I know React instead of Vue, or have experience with AWS and not Azure. What has contributed to my success is the willingness to learn new tools as the need arises.
What's not fine is having poured resources into a framework over the course of a few years, only for that framework to first cease to be necessary, and eventually become a barely-supported ball-and-chain.
This applies to almost everything released prior to HTML5. The problem is that re-writing isn't always an option, but the old stuff permeates almost every source file and is extremely expensive to decouple.
I suspect this will sooner or later apply to everything released immediately after HTML5. Eventually, everything used today will face the same fate.
There's something to be said for rejecting frameworks that aggressively inject themselves into code bases and which can't easily be extracted.
What's not fine is having poured resources into a framework over the course of a few years, only for that framework to first cease to be necessary, and eventually become a barely-supported ball-and-chain.
This applies to almost everything released prior to HTML5. The problem is that re-writing isn't always an option, but the old stuff permeates almost every source file and is extremely expensive to decouple.
I suspect this will sooner or later apply to everything released immediately after HTML5. Eventually, everything used today will face the same fate.
There's something to be said for rejecting frameworks that aggressively inject themselves into code bases and which can't easily be extracted.