Google's JavaScript framework AngularJS, currently in version 1.5, has quickly become one of the top frameworks for web development. Thanks to a series of concepts from professional software development, developers who previously had nothing to do with JavaScript now also have access to it.
The choice of a framework for developing a new web application has recently become increasingly easier with the introduction of AngularJS. However, since the first announcement of Angular 2 The tide turned over a year ago. Is it still worth setting up a new system on the "old" version today when the new one is almost ready for production? I would say yes.
What are the arguments in favor of Angular 2?
Angular 2 is certainly the more modern framework. The syntax makes heavy use of the current language tools from EcmaScript 2015. Alternatively, in TypeScript can be implemented. Many of the concepts of AngularJS 1, which are implemented in problems with large and complex applications were completely rethought. In addition, there were a number of Performance optimizations.
Overall, the new framework appears tidier, better thought out and also more user-friendly. Enterprise use well suited. Unfortunately, however, it is a completely new framework that cannot be easily migrated to from version 1.5.
Why AngularJS 1.5 is still an option today
As performant and elegant as the new language tools from EcmaScript 2015 are - developers who have previously gained experience in AngularJS 1.5 (or older) will not be able to use the new framework without Extensive familiarization phase can be used. The decision lies not only in the choice of framework version, but also in the The way in which development is carried out. To make matters worse, the Distribution in the community is not yet as large as with version 1. Questions and problems cannot yet be reduced to such a Extensive knowledge base to fall back on.
For AngularJS 1.5 there is now a Wide range of extensions such as the Component framework Angular Material. The market for Angular 2 looks even thinner. Ultimately, this means that more self-developed has to be. The Loss of efficiency In my opinion, this cannot be compensated for by the better language tools of Angular 2.
Companies that have not yet implemented a project with Angular 2 can not be based on previous experience. This makes the estimation of new projects more difficult and represents a Project risk difficult to calculate represent.
And what about the Further development of AngularJS 1.5? I assume that it will be available for at least another two years. Updates for AngularJS 1.5 is given, for example to to eliminate security gaps or optimize performance. The framework has now become so widespread that Google cannot afford to discontinue support overnight.
Recommendation: Continue to rely on AngularJS 1.5
I would still set up a new system on AngularJS 1.5 today without hesitation. Because the Availability of extensions, the existing knowledge among developers and IT departments and today's Sophistication lead to a Efficiency, that cannot yet be achieved with Angular 2.
Nevertheless, we must not neglect to look ahead. The Knowledge about Angular 2 can already be built up in parallel today, for example by smaller and non-critical projects can be realized with it. Also in the context of Prototypes the properties of the framework can be easily experienced.
In any case, it is worth a View of the on-board resources, that Google already provides for migration with Angular 2. This means that applications can already be developed syntactically close to Angular 2 in order to achieve a facilitate future migration.
Constant change in technology, especially in the Front-end area, is completely normal. Also the User needs in terms of usability are constantly increasing. Angular 2 will not be the end of the road and in a few years we will be faced with the same decision as today.
It is therefore much more important than the choice of framework to focus on the technological change. If a system is set up in such a way that Backend and frontend for example via web services decoupled from each other If the user interfaces are already in place, they can be replaced more easily. This means that development can be carried out very efficiently using established technologies without blocking the way for future updates.
Find out more about modern software development here
