ng3000: What is Angular 2 and 4, Why Did They Skip Angular 3, and Why Should I Update from Angular 1.x?

Mobile & Web

Whitley Bacon

Why Should I Care About Angular, Let Alone Angular 2 or 4 or Whatever Version They’re On Now?

Fergie delivered the ultimate jab when she declared in the Black Eyed Peas’ hit single “Boom Boom Pow” that she was “so three thousand and eight, you’re so two thousand and late!” One of Atlanta’s finest natives, Mr. Andre Benjamin, goes by Andre 3000 as his stage name. Let’s get on that 3000 level and talk about why we should care about (and maybe even use) Angular even with its semantic versioning. Although they’re not quite at ng3000 just yet, we can understand the big leaps made from Angular 1.x to Angular 2 and what’s in store for the future of Angular - from Angular 4 to beyond!

What We Will Cover:

  • What is AngularJS and what does it give me?
  • Why update from 1.x to 2 or 4 or… ? *TypeScript – the new JavaScript *Templates and directives ** ngModel ** ngFor ** ngIf ** ngClass
  • Filters vs. pipes
  • Modules; controllers -> components
  • @Decorators
  • CSS styling and encapsulation
  • What about React.js?

If you’re an Angular beginner, this will be a great starting point for you - you won’t have to try to do as much un-learning from Angular 1.x to get started with the newer versions. If you’re a seasoned ng-veteran, you can understand why those Angular folks have made some significant updates. And overall, we can all consider why we care about Angular. For example, why not use React instead? (Angular is better! Let me show you.)