A couple weeks ago, Stack Overflow published “The Brutal Lifecycle of JavaScript Frameworks”, a post about the short longevity of the frameworks we rely on as developers.
Like fuel to the fire, conversation about the best/most relevant/trendiest frameworks regained in force.
The amount of wheel reinventing in Javascript is well-known. Every few months or so, a new framework comes in, claiming to revolutionize our way to code. Some fail miserably and quickly disappear into oblivion, others gain “trend” status and hang in there. That is, until the next big thing sweeps them away.
Countless articles and hilarious memes mock this state of affairs:
(source: Bitovi)
But, is this really a bad thing?
While it sucks to invest in a framework only to see it fade into obscurity. I’m going to delve into why it’s actually a good thing that framework lifespans don’t last long.
Learning different frameworks will help you stay up to date.
Developers often get complacent as years pass by. Their trusty methods and logic have always worked, so why change? It’s mostly solid reasoning, except that adopting a new framework will often help us see things from a different angle.
For example: If you were happy doing direct DOM manipulation before, it’s refreshing to get the job done differently (i.e. Virtual DOM, data-binding …). There’s always new ways to accomplishing a task more efficiently. That’s the mindset that will help you improve as a developer, no matter your seniority level.
Your preferred framework will improve quicker.
It’s disheartening to see your framework of choice lagging behind in features. The fact that there’s so much competition coming out encourages the well-established technologies to improve faster. Your chosen framework will therefore be relevant for longer, until you decide something else would be a better tool.
Your job will be more exciting.
This may be a subjective point, but one to consider nonetheless. Having a stream of new technologies coming out helps us break the monotony and have a fresh start. All of a sudden, the old and mundane ways of accomplishing a task give way to a new shiny and efficient process. It’s like a breath of fresh air.
Newcomers will find it easier to get on board.
An ages-old framework with tons of documentation might be quite a challenge for a new developer. Having a new, simpler framework available is definitely more welcoming. A fresh framework community is also easier to get into than a established one, since everyone is just starting out.
It will help you stay competitive.
Last but not least, the competitive aspect. Let’s say you’re looking for a job change. It would generally be more difficult for you to find a job if everyone used the same framework.
It would be a game of “getting there first”, and people with years of experience would’ve already won.
Having a short framework cycle helps destroy this notion of “years of experience” that very often serves as a roadblock. The segmentation caused by all these frameworks means you’ll have less direct competitors for a given position. Also, you’ll be considered more for your skill than because of your years of experience, since some frameworks are barely a few years old.
These, and more reasons make this an interesting time to be a Web Developer.
