TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ok, let me explain: it’s going to be Angular 4.0

93 点作者 theodorejb超过 8 年前

16 条评论

joneil超过 8 年前
The title &quot;Angular 4 will be the next version of Angular&quot; had me ready to believe they were announcing another breaking change as big as Angular 1 -&gt; Angular 2. (The blog post&#x27;s title is &quot;Ok... let me explain: it&#x27;s going to be Angular 4&quot;).<p>It&#x27;s much more reasonable though: they&#x27;re committed to using Semver, so even a minor breaking change (like upgrading Typescript) will bump the version number. So they&#x27;re expecting the version numbers not to matter as much anymore, similar to how you no longer think of the version number of Chrome or Firefox too often.<p>And so they are asking the community to just call it &quot;Angular&quot;, not &quot;Angular 1&quot;, &quot;Angular 2&quot; and &quot;Angular 4&quot;. I do feel that this will make it harder to search for information, documentation or libraries specifically related Angular 1 though, if Angular 2+ is now just going to be called &quot;Angular&quot;, much like all the Angular 1 specific stuff.
评论 #13172885 未加载
评论 #13173367 未加载
评论 #13172642 未加载
评论 #13172652 未加载
评论 #13174040 未加载
评论 #13175414 未加载
hawkice超过 8 年前
The real story here is the seemingly casual way they&#x27;ve decided to start treating breaking changes. Deprecation periods are more polite than not having them, but saying that users need to be constantly using the most up to date version to get information about future support, and then introducing breaking changes into the current version more regularly, seems like a step in the wrong direction. Projects who lose a lot of community engagement due to breaking changes should be the ones who understand how much of a self-inflicted hassle that is best.
评论 #13172190 未加载
评论 #13174060 未加载
a-guest超过 8 年前
Angular 1 is NOT Angular 2 or higher.<p>Angular 1 and Angular 2+ are in essence completely different frameworks.<p>The &quot;Angular&quot; team should have picked a different name for their post-Angular 1 project.<p>The vibrant ecosystem of custom directives, etc., that surrounded Angular 1 must NOT be confused with the Angular 2+ project just so that everything can be &quot;one big happy Angular&quot;.
评论 #13176266 未加载
评论 #13181170 未加载
uncle_joe超过 8 年前
I think i officially hate semver. I seems a good idea at first. But updating the major version of Angular every 6 months, will not help us.<p>Or, semver should start to update its major version every 4 months, perhaps Angular devs will understand what the term JavaScript fatigue means.
评论 #13173238 未加载
评论 #13173323 未加载
评论 #13173291 未加载
评论 #13172648 未加载
评论 #13172961 未加载
miqkt超过 8 年前
It&#x27;ll be interesting to see how this change in versioning might impact recruitment for developers to service different versions of Angular projects. I guess this goes especially for recruiters who don&#x27;t really know (or care about) Semver.<p>I mean, there&#x27;s a rather huge rift (i.e. TypeScript, tooling, etc) between Angular 1 and 2, but this might not be the case for future consecutive major versions.
评论 #13173278 未加载
saghm超过 8 年前
First Windows, then Node, and now Angular. I worry that soon we&#x27;ll completely lose the ability to count properly.
评论 #13173964 未加载
SteveNuts超过 8 年前
Personally I can&#x27;t wait until Angular 7 is out by Q1 2017
评论 #13173137 未加载
EugeneOZ超过 8 年前
Too often they bring breaking changes. I hoped after stable release they will stop breaking things every two weeks or so, as it was in alpha, but looks like they still don&#x27;t understand that every breaking change stops development of projects for 1-2 days and this time is not free. I want to write code to solve business tasks, not just patching working code because of one more imperfection they found.<p>I can run HL1 on Windows 10 but my 5-months code for Angular is outdated.<p>Please, Angular team, be more pragmatic.
评论 #13173040 未加载
ben_jones超过 8 年前
I write angular 1 and 2 at work, so I like angular, but isn&#x27;t their a point where the powers that be should stop rocking the boat? All my colleagues who use other SPA frameworks really have their eye on the project&#x27;s pitfalls when they should at least keep up with its virtues.
ausjke超过 8 年前
what a chaos, so not only the internal changes break everything, even the version-numbers do it too, what&#x27;s the next surprise?<p>Isn&#x27;t angular for &quot;enterprise-large-project&quot; that requires stable-API and such?<p>just use either React or Vuejs
评论 #13173237 未加载
评论 #13173267 未加载
wnevets超过 8 年前
There were breaking changes going from 1.2 to 1.3, those weren&#x27;t any better than the possible breaking changes going from 2 to 4
eva1984超过 8 年前
Next next is Angular 8? Neat
latchkey超过 8 年前
Now I get to write &#x27;Angular &gt; 1&#x27; all the time.
m3kw9超过 8 年前
Weren&#x27;t people still trying to adapt to angular 3?
paulddraper超过 8 年前
tl;dr<p>Angular takes semantic versioning seriously, and while they will not be doing a 1 -&gt; 2 size change, they will need to increase the major version soon (Typescript upgrade, etc.)<p>They will also align the npm versions of the core packages. @angular&#x2F;router is at 3.3, so the next available major version is 4.
ascotan超过 8 年前
tl;dr<p>Angular versioning gets even more screwed up. It&#x27;s ok though because it&#x27;s javascript.
评论 #13173328 未加载