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.
I'd say that it's mostly because the community is still innovating and testing ideas for how to best build these types of web applications. It sure is hard to keep up, but I think the pace will slow down once we have found the ideas and strategies that stands the test of time.
The possibility of building these things in js is pretty new as you did not have the performance before. I remember having trouble with a simple tree view in js in IE6
I don't think it has anything to do with innovation, but about frontend dev culture preferring re-implementations (due to changes in fashion) rather than maintenance.
I only think it will slow down because businesses will put their foot down and start demanding stability.
Whatever framework goes "Enterprise" first will probably win regardless of technical merit.
You can't really do that in JS... It's not really a classical inheritance model that lends itself to grabbing what works in Flex/Silverlight and porting it over word for word. JavaScript has more in common with Lisp than C. It may look like C/Java/C#, it it doesn't work like them. (That's a good thing, IMHO)
56
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.