Skip to content

Instantly share code, notes, and snippets.

@ggregoire
Last active October 14, 2016 15:24
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ggregoire/f41ae88bb8e192ad70be690f19851a33 to your computer and use it in GitHub Desktop.
Save ggregoire/f41ae88bb8e192ad70be690f19851a33 to your computer and use it in GitHub Desktop.
Myth: JavaScript and tools deprecation

TL;DR

We have mostly used the same tools for years. People feel that React or Webpack are the new hype tools for cool kids, but React is there since 2013 and Webpack since 2012. A lot of companies still use Angular 1 (released in 2010, almost 7 years ago).

Complaints

I often read complaints about how fast the libraries/frameworks/tools are replaced with other ones in the front-end world.

For example in a recent Hacker News discussion:

the bigger issue [of the JS libraries] is the speed at which each one is replaced. [...] the absurd rate at which the JS community seems to adopt and deprecate libraries and frameworks and whatever else they're calling them today.

Or:

My main problem is the speed, and bad backwards compatability. Generally speaking if I take a 2 year old C,C++ or Java project, I can be sure I can update to recent libraries and everything will just work with minimal fixes. In Javascript it seems every time I pick a project up from a couple of years ago, every library version I was using is past end-of-life, and updating requires a major rewrite.

This feeling is quite interesting because the front-end world is not changing so fast. It's even pretty stable.

Chronology

If we look at the release dates of the main libraries/frameworks/tools used massively nowadays:

Libraries

  • jQuery : 2006
  • Lodash : 2012

Frameworks

  • Backbone : 2010
  • Angular 1 : 2010 (Angular 2 : 2016)
  • Ember : 2011
  • React : 2013

Builders

  • Grunt : 2012
  • Webpack : 2012

Transpilers

  • TypeScript : 2012
  • Babel : 2014

Analysis tools

  • JSHint : 2010
  • ESLint : 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment