The net benefit and multiple direction things are what makes it particularly frustrating. I wouldn't mind as much a new technology/technique/framework/etc if i

The net benefit and multiple direction things are what makes it particularly frustrating. I wouldn't mind as much a new technology/technique/framework/etc if it were a clear, direct, step and meaningfully better than what came before. It's especially hard to be considering what technology/stack to recommend as being easy to develop in and maintain for LOB enterprise developers who will be maintaining an app (without rewrites) for ten years or so. Right now we're using Knockout but it's feeling a bit grumpy in various respects so I've been looking into React. But still it is common to have breaking changes, and then there's the whole ES5/ES6/TS split. I need something that our devs can do a Google search "How do I do <X> in <Y>" and nearly copy-paste the result. Knockout has been particularly good for that because it's evolved very slowly and every example for it is in ES5. Microsoft has wedded themselves to Angular for ASP.NET 5, but it looks like it's Angular 1. Meanwhile Angular 2 looks much better but again splits across ES5, ES6, TS, and Dart... If someone searches "How do I do <X> in Angular?" who knows what combination of assumptions might be unlying that answer. As much as I'd prefer to use something like React, I think shops with the combination of lower skilled staff and longer term maintenance projects (like ours) will need to wait until, hopefully, the industry calms down and settles on a set of new standards. Microsoft seems to have gotten sucked into the "do everything a million different ways" spaz attack with ASP.NET 5, but meanwhile Apple seems to be doing it right with a narrow, opinionated set of technologies with a well understood evolutionary path and specific tools for specific jobs.