Re:Why Learning Angular 2 Was Excruciating
by mambodog on Monday September 19, 2016 @08:36PM
(#12536004)
> I'd like to point out that React has had breaking changes roughly 6 or less months apart
When? Can you cite an example? Keep in mind that for most breaking changes React typically goes to a deprecation warning for the duration of a major release instead of hard-breaking changes, so in reality you have roughly double the time between truly breaking releases, generally speaking.
Re:Why Learning Angular 2 Was Excruciating
by Bahamut on Monday September 19, 2016 @09:19PM
(#12536238)
Take a look at the changelog for breaking changes - they even timestamp it.
That is true about the deprecation, although some of the earmarked breaking changes have been quite painful too.
Hopefully the Angular team takes this route for planned breaking changes & apply engineering to ease compatibility.
Re:Why Learning Angular 2 Was Excruciating
by WalterSear on Monday September 19, 2016 @07:51PM
(#12535731)
That's a really good point, that I should have been aware of.
The more I reflect, the more I see this as about poor expectation management and messaging from the Angular team than an actual story.
The scope of the breaking changes matter more, and that story has yet to be told.