Why original: Hui Zhi network
Angular1.x obviously very successful, then, why do we have to turn violently to Angular2?
Limitations of performance
Angularjs was originally an internal tool for designers to quickly build HTML forms. Over time, various features are added to suit the development of applications in different scenarios. However, due to the initial architectural constraints (such as bindings and templating mechanisms), performance improvements have been very difficult.
Fast-changing Web
In terms of language, ECMASCRIPT6 's standards have been completed, which means that browsers will soon support new features such as modules, classes, lambda expressions, generator, and so on, which will significantly change the development experience of JavaScript.
In terms of development patterns, Web Components will also be implemented quickly. However, existing frameworks, including angular1.x support for Web Components, are not good enough.
Mobile
Think about 5 years ago ... The current computing model has changed dramatically, with phones and tablets everywhere. Angular1.x is not specifically optimized for mobile applications and lacks key features such as cached precompiled views, touch support, and so on.
Simple to use
To tell the truth, angular1.x is too complicated, the learning curve is too steep, which is daunting. The angular team wants to encapsulate the complexity in Angular2 better, making the exposed concepts and development interfaces simpler.
<!doctype html>
<meta charset= "Utf-8" >
<title>why angular2</title>
<body>
</body>
Angular2 Getting Started