You guys have probably heard some of the backlash to Angular 2.0. This article offers an interesting counterpoint that I felt worth considering.
I saw this news item pop up when I was searching for something AngularJS in the last days; figured it was just some hater. Forced myself to read it and got me thinking. In my current experiences, I see the two sides of the argument.
At my day job, I am asked to support ancient (20+ year) hodge podge Perl code that actually does not do a whole bunch but is complicated because it grew organically and never was cleaned up. The problem is that management has never wanted to spend the resources to modernize the applications (and management has no development background). At this point, we are paralyzed by our existing code base and are really only bandaiding things as they break. Definitely a bad place.
On the other hand with my side business, I squeak in development projects here and there using fairly modern technologies when I have time. In the last four years alone, I have changed out some tool in my toolkit about once every six months. I like the term Developaralysis as shared on this forum. This is a better place, but at times (like when I read up on the changes in AngularJS) I think can't we just slow down a bit.
But... Of the two choices, I vote for change; especially if that change allows us to develop faster and easier (as usually is the case).
Unfortunately your perl code base represents a frequent case in business applications. By definition, a framework is what a system stands upon. Making the choice of which framework to use can be a difficult one. Web is definitely in a state of transition right now which makes being married to a framework tricky. Those who can't afford the prospect of rewriting an application or risk leaving it unsupported simply have to make a tough decision-- risk it or go with something that's more stable like ExtJS or Knockout.
The haters are loving this and the typical argument is that Angular is either a) developed by a bunch of kids that don't understand proper software development or b) championed by Google which, of course, gives 0 fucks about it's users and will probably abandon Angular altogether in a years time anyway.
Igor (project lead for Angular) has made somewhat of a statement about the rage regarding the 2.0 syntax change and the general vibe is that it's all about starting a discussion and working on a solution as a community. Say what you will about the maturity level or the way this is all being handled but I like where this is all headed.
In case anyone's wondering, there is a valid argument for the syntax change and it has to do with the future of web development. Building out compatibility for the future means the Angular team has a lot to deal with but they're trying to ensure that the Angular API will continue to be functional and stable in the new world of web components. The new syntax itself isn't even completely finalized yet as it's still got some issues to work out.