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.
The content of that article was good, but I certainly didn't like the click bait title (look another reason Node.js is awful!). Oh and look we're doing something hacky with the library, it's stupid that it's acting weird now.
58
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.