— I Am Devloper (@iamdevloper) June 14, 2015
This response used to make me panic. I had no idea what to say. There are so many JS frameworks out there, and someone still tentatively wading through the shallows of this diverse ecosystem can’t possibly know the “right” one to choose. So I would stumble through an explanation of how I was still evaluating the options before committing. (At which point I could just settle back and listen to the equally inevitable impassioned explanation of why Ember/Backbone/insert-your-personal-platform-of-choice-here is the ONLY reasonable choice).
I’ve been plugging away at programming long enough to understand two important things: first, the moment you commit to a framework, you are chaining yourself to a technology that will be deprecated sooner or later. Probably sooner, given the rate that new cool kids frameworks are popping up these days like Tribbles in Star Trek.
Second, when all is going well, frameworks will absolutely save you some time. Maybe even a small team of folks all working on the same thing. But. When are you ever going to be working on only one project? And in the far more likely scenario of more than one team working on more than one app — do you really think all team leads are going to agree on a single winner from the whole JS framework tower of Babel?
Because at the end of the day, I’m not an Angular developer. I’m not a React or Vue or Backbone or Ember or etc. etc. etc. developer.
Feature image via FreeStockPro.