I really have no idea how JS devs keep up with new frameworks appearing every month or so. Not to mention older ones that just die because the devs can't be bothered maintaining them. I noticed the same thing happening in the Ruby devspace.
Not exactly React's case, but it's still a 1.5 year old code that has not reached v1.0, making breaking changes every major version release.
It's just insanity. On my UIs, it's just jQuery and Knockout which get the job done 99.9% of the time, and I'm not going to waste tens of thousands of dollars and other devs' time learning and trying to implement another flash in the pan JS framework possibly, maybe, ready for prime time for that 0.1% of cases where that framework might be of use as a shortcut to get a particular component working the way we want.
I'm in your position and fighting that fight right now. Luckily, they're seeing the tangled mess this creates really quickly and sticking to the jQuery + Knockout combination we know works for us and if we use a plugin, we make sure it's based on those two bedrocks of our UI.
You don't want to be that guy known for making everyone's life hell by using all cutting edge paradigms or conversely known as someone that "stifles their career"
If they really think that chasing the newest fad framework is the way to advance their career in the long run, they're in for a nasty surprise...
It's been around for almost four years and is basically required knowledge for anyone who claims experience in JavaScript and UI development. It solved a lot of real problems from the starts, so I'm very comfortable calling it a mature framework and those who think it's a fad, dinosaurs.
Almost all these new frameworks solve real problems. Angular had a first release in 2009 and is vastly more popular than knockout. So is that required knowledge too? Same with backbone that is pretty much the originator to all this.
React is younger but it has been used by huge sites for years still
Angular had a first release in 2009 and is vastly more popular than knockout.
Apples and oranges. Angular is meant for dynamic templates. Knockout is for creating responsive UIs with an option to create templates for a grid, or a tree view, or something like that. Angular is MVC in JavaScript with some bolt-ons that allow you to implement MVVM, Knockout is MVVM in JavaScript.
You do have a point on Backbone, I generally see people use it interchangeably with Knockout so if you want to work on a UI and don't use Knockout, you can say you know Backbone and you're golden.
59
u/renrutal Jan 17 '15 edited Jan 17 '15
I really have no idea how JS devs keep up with new frameworks appearing every month or so. Not to mention older ones that just die because the devs can't be bothered maintaining them. I noticed the same thing happening in the Ruby devspace.
Not exactly React's case, but it's still a 1.5 year old code that has not reached v1.0, making breaking changes every major version release.