Angular 2 final version officially released

On September 15, the final version of Angular 2 was officially released.

What does it mean to be the full platform successor to Angular 1 -- the final release of Angular 2?

  • Means that the stability has been verified by a wide range of use cases;
  • means optimized for productization, file size, and performance;
  • It means that pre-compilation technology and built-in lazy loading mechanism can be used to ensure that the fastest and smallest application can be released and span browser, desktop and mobile platforms;
  • This means that the Angular CLI and style guide for developers has been greatly enhanced.

The release of Angular 1 as an emerging web technology solved the problem of how to develop. Now, the challenge for developers is that applications need to support a wide variety of devices. In the final version of this release, there are already more capable routers, forms, and other core APIs.

Now it's possible to build amazing apps on any platform. If you like the way you currently work, the modular and flexible Angular gives you the freedom to use your favorite third-party library -- or write one yourself!

From now on, let's build Angular together with the open source community. At the same time as the final version of Angular 2 was released, some development tools also supported Angular 2. Among them, Wijmo was the most  responsive one . Currently, Wijmo has provided support for the final version of Angular 2.

 

What's next?

In the near future, the Angular development team will be working on the following:

  • Fix bugs, make non-breaking changes to APIs marked as stable
  • More guides and online examples for use cases
  • More work on animation
  • Angle Material 2 
  • Taking WebWorker out of the lab
  • More features and languages ​​developed for Angular Universal
  • faster speed, smaller load

Semantic Versioning

为了在 Angular 的稳定版中,更容易地管理依赖,从 Angular 2.0.0 开始,将逐渐向“语义化版本”迁移。今后的 Angular 版本,将遵循 semver 所描述的 MAJOR.MINOR.PATCH 方案:

  1. 当不兼容 API 向稳定 APIs 变更时,添加主版本号
  2. 添加向后兼容的功能时,添加次版本号
  3. 修复向后兼容 bug 时,添加补丁号

迁移 Angular 到语义化版本,可以确保快速访问到组件和工具生态系统等的新特性。产品应用的稳定开发环境,还是会依赖于主版本之间迁移的稳定性,同样也受益于 bug 的修复和新的 APIs。

原文链接:http://angularjs.blogspot.hk/2016/09/angular2-final.html

 

 

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326583700&siteId=291194637