News for hackers. Stuff that matters.
Re:Why Learning Angular 2 Was Excruciating by WalterSear on Monday September 19, 2016 @05:51PM (#12535080)
This release cycle is fine so long as you don't rely on anything but Angular 2.

As soon as you rely on packages that support Angular 2, the 'good and ready' argument breaks, since you can't start till all the packages you rely upon have already made the upgrade, and you can't take to long either, because you can't expect further work or fixes to be made to older versions of the packages.

12-month breaking changes, that would have made sense.

Re:Why Learning Angular 2 Was Excruciating by seangrogg on Monday September 19, 2016 @07:12PM (#12535556)
This makes the improper assumption that you're forced to upgrade. The code for Angular 2 will not evaporate when Angular 3 appears - at that point the choice to upgrade to the latest version is just that: a choice. You are free to wait until Angular 4 comes out before you adopt Angular 3 if you want to make sure the ecosystem around it is solidified.
Re:Why Learning Angular 2 Was Excruciating by WalterSear on Monday September 19, 2016 @07:56PM (#12535765)
I've been 'forced to upgrade' in the past by issues in dependencies that won't be fixed, with other dependencies not updated yet. It's a sticky wicket.

That said, breaking changes every six months seems to be commonplace in major open source packages. My initial reaction was 'OMG, now they want to repeat the Angular 2 debacle every 6 months?!?', which doesn't seem to be the case.

Re:Why Learning Angular 2 Was Excruciating by slmyers on Monday September 19, 2016 @08:27PM (#12535950)
It sounds odd to me that an app would include packages that have dependencies on a framework. I'm having a hard time picturing an example, can you provide one?
Re:Why Learning Angular 2 Was Excruciating by WalterSear on Monday September 19, 2016 @09:04PM (#12536150)
I could have worded it better.

http://ngmodules.org