The Angular team releases a roadmap and demonstrates how to integrate with React Native, angularreact
This article is from the article I translated on InfoQ Chinese site, the original address is: http://www.infoq.com/cn/news/2015/06/angular-2-react-native-roadmap
Not long ago, at the Angular U conference in San Francisco, Brad Green, Igor Minar, and Misko Hevery delivered speeches and elaborated on their statement at the ng-conf Conference at the beginning of the year, it also provides a roadmap for Angular in the second half of 2015.
Minar demonstrates some new developments in Angular since January March. It is worth noting that these are some "experimental" features. He proposed the idea of dividing Angular into core functions and Renderer. Through the separation framework, they hope to enable the new way to use Angular. The first is the following three fields:
For Web performance, Angular can assign most non-UI work to WebWorker through the split framework. The UI must be in the main thread so that a separate Renderer can work and the two parts can communicate with each other. Minar said:
We are thinking, "Can we migrate the entire application to WebWorker so that all business logic and data acquisition and processing can be separated from the main thread ?" In addition, "can I migrate the framework itself to WebWorker? In this way, all the services provided by the framework and various checks do not have to run in the main thread ".
After the Angular team met the React team, an outstanding question was "what if Angular and React Native are integrated"? In new scenarios, the core remains unchanged, but the Renderer can support new platforms, such as iOS and Android.
Minar demonstrates how to insert the React Native tag to Angular and run Angular JavaScript in the Native iOS Shell. The team used Telerik and its NativeScript platform to achieve these objectives with the React team, in contrast to the scenario of rebuilding from scratch. This demo is located at GitHub.
Angular developers have long been looking forward to solving problems such as improved startup time and SEO through server rendering. The architecture proposed by the team also provides possible solutions for the problem.
For Web developers, architecture changes are transparent to a large extent. Google has published a separate architecture for developers to review.
Green also updated Angular 2's completion time. He does not give a specific date, but lists the stages of the project prior to release. At present, the team is improving the core and has received feedback from the team that is migrating Google internally. When the core is complete, they will continue to improve the API, improve the performance and documentation.
Green also talked about Angular 1.x and its position in the future roadmap. He said, "The focus of Angular 1.5 will change." Google is also developing new automated migration tools, some of which have been used internally. "We will see what reflects the community's concerns," he said. They are also writing a guide to help developers complete the migration. For more information about the speech, watch the video or download the speech.
Angular U is 2nd of the three conferences attended by the Angular team this year. Angular Connect will be held in London in May 3rd.
View Original English text:Angular Team Provides Roadmap, Demos Integration with React Native