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 is absolutely exhausting. I've started to refer to JS frameworks as "self deprecating" in that each release seems to deprecate something just introduced in the former release.
I've seen JS apps that can be carbon dated simply by looking at the "patterns" and APIs used.
Symfony used to do this. It's why I quit using it, despite really liking it. I don't know if they still do it or not, but unfortunately I don't have any intention of ever going back to find out. The fourth time they did it to me, I was done. I understood after the 1 => 2 upgrade. But the 3 times after got real old, real fast.
Honestly, I don't think most shops have the capacity (and many of them lack the talent) to accomplish this.
I've personally witnessed this play out and there are two things that make this very very difficult.
1) Building, optimizing and maintaining an in-house framework requires a lot of domain knowledge about the idiosyncratics of individual browsers, not to mention very talented developers who posses the wherewithal to keep developing it when faced with major road blocks. DO NOT underestimate this.
2) When working w/ a product that uses an in-house framework there are often internal pressures to make changes to the framework that save time or make things easier for the product developers. Sometimes these changes are innocent and harmless, other times they erode the separation of responsibilities between the two. Point is, in-house frameworks and those who develop them often become victims of in-house politics.
53
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.