A team of Excellians recently attended ng-conf 2017 in Salt Lake City, UT, the premiere meeting of Google, Microsoft, open-source and community leaders for the Angular and AngularJS Projects. AngularJS Angular 1.x is now called AngularJS and has 1,000,000+ active developers still using it by Google’s accounting. This number is likely the peak for the […]
Angular 1.x is now called AngularJS and has 1,000,000+ active developers still using it by Google’s accounting. This number is likely the peak for the revolutionary, but troubled, web framework. AngularJS was never designed to be as capable as it is and used at the large scope and scale it has been utilized by developers. It was inevitable for the framework to plateau.
Many new projects starting today still leverage AngularJS, instead of the new version of Angular, because of vast architectural, conceptual and technological changes. These changes are for the better, mind you, but it is expensive to train developers and it is difficult to have to learn a brand-new framework.
The new versions of Angular are now simply called, Angular – and for good reason. Version 2, first announced in late 2014, finally released in late 2016, marks the beginning of a new platform, not merely a browser bound framework. With Angular you can target browser, mobile (Ionic), desktop (Electron), and server-rendered (Universal) apps.
Angular 4 was released on March 2017 only 6 months after version 2. Version 3 was notably skipped, because of internal component versions falling out of sync due to semantic versioning with semver.
The Unix world has been using odd-even version numbers to distinguish between experimental and stable versions of software and protocols since, well, forever. This is why, you know about IPv4 and IPv6, but never heard of IPv5.
Even numbered releases are marked as long-term support (LTS) versions that are guaranteed to receive non-breaking features and performance improvements for a year and critical security patches 18 months after initial release. This release cadence ensures that the community is happy with cutting edge features and enterprises can rely on Node in production due to its predictable release and support windows.
Tl;dr – you deploy Node LTS on your server and you move on. Read more about why I thought 2016 was the year of Node shined.
What does this mean for you?
Check out my 6-part blog series on Building Scalable and Beautiful AngularJS Apps using Angular 1.5, AngularJS Material, ngComponentRouter and browserify to build apps that are architected like the Angular platform apps, so that your team can leverage their existing skills and be introduced to the new concepts of Angular. Once you and your team become familiar with the concepts, it’ll be much easier to switch to the new Angular platform.
Otherwise, head over to Angular.io and begin your learning process today.
But Wait There’s More
Stay tuned for these blogs and more from ng-conf 2017 by the ExcellaJS team:
In my previous post, I walked through common scenarios and attempted to present a high-level...
At ng-conf 2018, the Angular team unveiled an astonishing suite of new features to come...