This article is from my translation of the Infoq Chinese station, the original address is: Http://www.infoq.com/cn/news/2015/06/angular-2-react-native-roadmap
Shortly before the angular U conference in San Francisco, Brad Green, Igor Minar and Misko hevery jointly delivered a speech, again explaining the declaration at the NG-CONF conference earlier in the year and giving a roadmap for angular in the second half of 2015.
Minar shows some of the new developments angular has made since March.
It is worth noting that these are "experimental" features, he proposed the idea of dividing angular into split into a core function and renderer. By separating the framework, they want to be able to open new ways to use angular. The first is for example the following 3 areas:
- Improved performance
- Rich Mobile Experience
- Service-Side rendering
For Web performance, the cutting framework allows angular to hand over most of the non-UI work to Webworker. The UI must be in the main thread. This allows the individual renderer to work, and the two parts can communicate with each other. Minar said:
We are thinking, "Can the entire application be moved to Webworker so that all business logic, all data acquisition and processing can be removed from the main thread?" "In addition," can the framework itself be moved into Webworker? All the services provided by the framework and the various checks do not have to be performed in the main thread. "
After the angular team met with the react team, an unanswered question was "what if we were to integrate angular with react native?" In the new scenario, the core remains the same, but the renderer is able to support the new platform. such as iOS and Android.
Instead of rebuilding such a scenario from scratch, the team used the Telerik and its Nativescript platform and worked with the react team to achieve these goals.
The demo is on GitHub.
For a long time, angular developers have been looking forward to solving issues such as improved start-up times and SEO through server-side rendering.
The architecture presented by the team also provides a possible solution to the problem.
For web developers. The changes to the architecture are largely transparent. Google has disclosed a separate architecture for developers to review.
Green also updated the completion time of angular 2. He did not give a detailed date, but listed all the stages of the experience required for the pre-announcement project. Right now, the team is on the right core and gets feedback from the team that is migrating within Google.
When the core is complete, they continue to be intact APIs, improved performance, and documentation.
Green also talked about the angular 1.X and its location in the future roadmap. "The focus of Angular 1.5 will change," he said.
Google is also developing a new self-motivated migration tool that has been used internally.
He said. "We will see what reflects what the community cares about," he adds. In addition, they are writing guidelines to help developers complete the migration.
To learn more about the presentation, watch the video or download a speech.
Angular U is the 2nd session of this year's Angular team to participate in the 3 Conference session. The 3rd session of Angular Connect will be held in London this October.
View English text: Angular Team provides roadmap, Demos integration with React Native
Angular team announces roadmap and demonstrates how to integrate with react native