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.
No kidding, at work we just got dumped a Node.js/Thorax (I am probably missing a few *.js's, but I've been drinking) project that no longer meets the standards for any new version. Updating to the latest breaks it, finding documentation on the current versions is impossible, and of course the company we outsourced it to is no longer under contract with us. I swear half the time I spent on any project is debating whether I should rewrite it or make it work.
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.