Deborah's Developer MindScape

         Tips and Techniques for Web and .NET developers.

April 4, 2016

Why Angular? Why Angular 2?

Filed under: Angular,JavaScript @ 10:52 am
Tags: , , ,

Why Angular and not some other JavaScript framework? (And there are lots of JavaScript frameworks out there!)


· Angular makes our HTML more expressive. It powers up our HTML with features such as if conditions, for loops and local variables.

· Angular has powerful data binding. We can easily display fields from our data model, track changes, and process updates from the user.

· Angular promotes modularity by design. Our applications become a set of building blocks, making it easier to create and reuse content.

· And Angular has built-in support for communication with a back-end service. This makes it easy for our Web applications to integrate with a backend service to get and post data or execute server-side business logic.

No wonder Angular is so very popular with Web developers!

With so many developers already using Angular 1, why do we need an Angular 2?


· Angular 2 is built for speed. It has faster initial loads, faster change detection and improved rendering times.

· Angular 2 is modern. It takes advantage of features provided in the latest JavaScript standards and beyond such as classes, modules, and decorators. And it leverages Web Component technologies for building reusable user interface widgets. Yet it supports both green field and legacy browsers: Edge, Chrome, Firefox and Internet Explorer back to IE 9!

· Angular 2 has a simplified API. It has fewer built-in directives to learn, simpler binding, and a lower overall concept count.

· And Angular 2 enhances our productivity to improve our day-to-day workflow by providing a consistent pattern for writing our code.

For more information on Angular 2, check out my “Angular 2: Getting Started” course from Pluralsight.


  1.   Matt — April 5, 2016 @ 11:08 am    Reply

    Since you have worked with Angular 2 more than most, are you more comfortable with the html decorators and annotations in Angular 2 as opposed to Angular 1?

    I’m referring to the funky, cryptic symbols Angular 2 uses: *, (), [] #.

    The HTML templates for Angular 2 I’ve seen just feel…wrong. The syntax seems to be fighting against HTML rather than acting as a compliment.

    While I have not used Aurelia, I think this older blog post illustrates the difference well between the html you see in Angular 2 vs the more readable attributes in Aurelia.

    Perhaps libraries with more Angular 1 style syntax such as Aurelia and Vue.js will increase in popularity as a result.

    Another way to look at it is with good ol’ (or mabye bad ol’) ASP.NET web forms. Imagine if back in the day the syntax used to define attributes on a web forms control was similar to Angular 2 rather than the more descriptive, easier to read attributes they use. I don’t think developers would have been happy!

    •   deborahk — April 14, 2016 @ 9:32 am    Reply

      Hi Matt – Yes, I felt the same way about all of the symbols when I first looked at it. But my understanding is that for the tooling to recognize the different types of things (such as bindings and structural directives) they needed some way to mark them up. And having parenthesis around an event, for example, means we can define our own events and not have to wait for Angular to create an ng-something for us.
      Hope this helps.

  2.   mehdi — April 11, 2016 @ 3:17 am    Reply

    @matt about the funky symbols you’re right about it when you’re starting out , i was like that when starting out after a little coding it makes sense , specially when you put the meaning in your mind like why this symbol is one-way data binding and why it becomes a two-way data binding the other way etc.

RSS feed for comments on this post. TrackBack URI

Leave a comment

© 2022 Deborah's Developer MindScape   Provided by WPMU DEV -The WordPress Experts   Hosted by Microsoft MVPs