4 ms·

This is a bit of a rant, but anyway... There are currently two posts on Angular on the front page of HN. Both have quickly devolved into multiple rants decryin

This is a bit of a rant, but anyway... There are currently two posts on Angular on the front page of HN. Both have quickly devolved into multiple rants decrying "breaking changes", which can be traced back to the initial Angular 2.0 announcement: http://angularjs.blogspot.com/2014/10/ng-europe-angular-13-and-beyond.html http://angularjs.blogspot.com/2014/10/ng-europe-angular-13-a... This really speaks to the importance of communication around these announcements. If you pay attention to what's actually communicated, yes, there will be a migration plan for 1.x apps. Yes, 1.x will be continued to be supported for much longer than the lifetime of most of your little startups - sorry to break it to you. Yes, 2.x is a much-needed step forward for SPA app development. BUT, when Angular 2 was announced, it was announced too early - they shared the fact that breaking changes were coming, and that AT THAT TIME, there wasn't a plan in place for migrating 1.x apps. That poorly phrased communication has since dominated any discussion about Angular 2, very much to the detriment of the project. It's the same thing as the Flickr, Instagram, Facebook, etc TOU changes that caused such a brouhaha in recent years, except that you would think technically-minded developers would be able to parse the actual information.

sergiotapia 12y ago
I understand where you're coming from - but that singular announcement left a TERRIBLE taste in my mouth for Angular. I won't use it for any project, hobby or otherwise. Compare it to Ember where they are bending over backwards to provide free improvements and a sane backwards compatible approach. Why bet your entire business on a framework that has such poor communication skills? (Again: Assuming what you're saying is correct ;) )
- grumblestumble 12y ago
  Yeah, very valid point. Ember's outward communications are a really good model of how to deal with this stuff - unfortunately I just can't imagine myself working with the framework. The thing I find most hilarious is that the followup to the "OMG Angular 2.0 is making breaking changes" herdthink is usually "Let's all move to React 0.12!".

sergiotapia 12y ago

I understand where you're coming from - but that singular announcement left a TERRIBLE taste in my mouth for Angular. I won't use it for any project, hobby or otherwise. Compare it to Ember where they are bending over backwards to provide free improvements and a sane backwards compatible approach. Why bet your entire business on a framework that has such poor communication skills? (Again: Assuming what you're saying is correct ;) )

grumblestumble 12y ago
Yeah, very valid point. Ember's outward communications are a really good model of how to deal with this stuff - unfortunately I just can't imagine myself working with the framework. The thing I find most hilarious is that the followup to the "OMG Angular 2.0 is making breaking changes" herdthink is usually "Let's all move to React 0.12!".