MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/javascript/comments/52u9a4/angular_2_final_released/d7ob1fd/?context=3
r/javascript • u/Click_Clack_Clay • Sep 15 '16
190 comments sorted by
View all comments
Show parent comments
5
Those breaking changes were specifically because Angular2 wasn't done. Google is moving to semver now, so that shouldn't be an issue going forward. It definitely isn't a "reason not to use it".
2 u/rk06 Sep 15 '16 edited Sep 15 '16 Logically speaking as angular team has said that they will follow semver, you are definitely correct.But practically speaking: once bitten, twice shy. 2 u/[deleted] Sep 15 '16 what were you bitten by? An open dev process? Would you rather they did everything behind closed doors and only presented the final result? 1 u/[deleted] Sep 15 '16 If the release candidate is not a release candidate, do not call it a release candidate.If you are unwilling to do that, then I would prefer you work privately, yes.
2
Logically speaking as angular team has said that they will follow semver, you are definitely correct.
But practically speaking: once bitten, twice shy.
2 u/[deleted] Sep 15 '16 what were you bitten by? An open dev process? Would you rather they did everything behind closed doors and only presented the final result? 1 u/[deleted] Sep 15 '16 If the release candidate is not a release candidate, do not call it a release candidate.If you are unwilling to do that, then I would prefer you work privately, yes.
what were you bitten by? An open dev process? Would you rather they did everything behind closed doors and only presented the final result?
1 u/[deleted] Sep 15 '16 If the release candidate is not a release candidate, do not call it a release candidate.If you are unwilling to do that, then I would prefer you work privately, yes.
1
If the release candidate is not a release candidate, do not call it a release candidate.
If you are unwilling to do that, then I would prefer you work privately, yes.
5
u/Mael5trom Sep 15 '16
Those breaking changes were specifically because Angular2 wasn't done. Google is moving to semver now, so that shouldn't be an issue going forward. It definitely isn't a "reason not to use it".