You may have noticed that Angular 2 is radically different from the Angular you might have grown accustomed to. It introduces TypeScript, RxJS, and a component based development approach that is more in line with how modern web applications are being assembled.
This is all fantastic news!
Buuuuutttttt…
Does this mean we need to jump feet first into this new era of Angular? What if we have an existing “legacy” Angular app? What can we do now to start incrementally working towards the new hotness?!?
Great questions, and we’ve got some thoughts on the subject.
Lukas Ruebbelke and I have spent considerable time over the last several years traveling around to companies teaching them how to build solid Angular 1.x applications. The questions above are actual questions asked by devs on a regular basis over the last year or so. Making the leap into FULL ON ANGULAR 2 just isn’t realistic in a lot of circumstances, so we are going to discuss alternatives.
The first step is to fully embrace ES6. It’s freaking awesome, and a major step in the right direction. Then we want to start looking at the patterns we use for building applications. Specifically we want to double down on the idea of building modular components, which we can totally do with Angular 1.5 today.
To help you out, Lukas has created a course on using the patterns and practices you can expect in Angular 2 today in your Angular 1.x applications.