Angular2 - First Impressions

Edit · Apr 6, 2015 · 18 minutes read · AngularJS Angular2 JavaScript

On 18th of September 2014 was pushed the initial commit of version 2.0 of the AngularJS framework. A few weeks ago the core team at Google, published AngularJS’ 2.0 website and gave a couple of talks on ng-conf about their new router, change detection, templating, etc. I’m passionate about AngularJS since its early versions so I decided give it a try using the quick start. In the meantime I and also created an angular2-seed project for my test, dummy projects. In order to have a better understanding of what is going on (and handle the lack of documentation) I dug inside their source code. I had great time doing this, what I saw was one of the most well written and smartest pieces of software I’ve ever read. Soon I’m planning to expand my paper “AngularJS in Patterns” with design patterns used inside Angular2.

In this blog post I’ll share my first impressions of the framework and I’ll try to keep them as objective as possible, despite my affinity to AngularJS. I’ll start with the general changes and after that keep going into details.

Written in TypeScript

As Microsoft already published, Angular2 is written in TypeScript. There are a couple of advantages using strongly typed language and a couple of more advantages using TypeScript specifically. By “extended version of TypeScript” I mean, TypeScript with added annotationsdecorators (its syntax looks similar to the annotations in Java).

JavaScript Dialects

And here are some of the main advantages using TypeScript as statically typed language:

  • Using statically typed language:
    • You get type errors compile-time and runtime (traceur transpiles the source code to one with runtime type assertions with rtts (runtime type system), see below the sample gulp-traceur config) . This way it’ll be easier to debug your code and you will be more secure that what you’ve developed (in this case Angular2) actually works. When it happens to develop a single-page application, bigger than 10k lines of code, the lack of compile-time checking leads to quite painful experience, even with big test coverage of your code.
    • You get better auto-completion by the text editors and IDEs. WebStorm 10 supports TypeScript 1.5 + decorators and ES6 modules. For vim you can use the typescript-tools, which could be integrated with emacs and SublimeText. You will get hints for method names, parameters, parameters types by your editor/IDE for each AngularJS method (yes, with Tern.js or Flow you can get the same experience but based on JSDoc or some very sophisticated decisions made using the AST of your code, now it’ll be much less tricky).
    • The JavaScript VM is able to make better code optimizations. Since when we define that given property/variable has specific type we sign some kind of contract with the JavaScript VM, this way it is much easier for it to reason about the types of the variables, which are being used and to do better runtime optimizations (for instance).
  • About TypeScript:
    • TypeScript is superset of ES6, which is superset of ES5 (ES5 ⊆ ES6 ⊆ TypeScript). Angular2 production build is being transpiled to ES5 in order to be executable by the modern browsers. You also can chose whether you want to write your code in ES5, ES6, TypeScript (of course if you chose ES6, TypeScript your code should go through a process of compilation in order to be transpiled).
    • TypeScript is being one of the best languages, which are being transpiled to JavaScript, which has allows optional type checking.
    • TypeScript is developed and supported by Microsoft, which gives us stability that it is unlikely the support to be dropped unexpectedly.

In the past I’ve actively considered using a language with static type system, for building my single-page apps. I was thinking mostly about Dart, the fact that the types there are optional wasn’t a concern, because in the critical areas of your code you would be able to use them and you’ll get all the benefits a statically typed language provides. TypeScript seemed like a nice language but I never thought would shine the way it does now. Anyway, TypeScript seems like a better option because of its syntax - much easier to learn given it is superset of ES6.

Quick FAQ:

Does the runtime type checking lead to slower execution of your application?
Probably yes, but you can disable it when you plan to deploy your app in production.

Shold I use TypeScript for my Angular2 application?
It is not necessary but I’d recommend you do, because of all the benefits I mentioned above. Actually you even don’t have to use ES6, but I’d even more strongly recommend you do.

Alright, if I do use TypeScript…how can I debug it when my browser supports only ES5? Should I debug the generated code?
Traceur will create source maps for you. You will debug the code you’ve already written, not the ES5 generated by the transpilation process.

TypeScript source maps

How can I take advantage of it? Should I use Visual Studio or something?
No. You can use the traceur compiler and a task runner, like gulp or grunt, with the corresponding plugins (here and here). The actual type checking should be implemented inside external “assertion” library. For example, Angular2 uses the rtts_assert module.

Here is a sample configuration of gulp-traceur, using type assertion:

gulp.task('build', ['copy'], function () {
  'use strict';
  return gulp.src([
      // some files here
    // some other plugins
      modules: 'instantiate',
      sourceMaps: 'inline',
      annotations: true,
      memberVariables: true,
      typeAssertions: true,
      typeAssertionModule: 'node_modules/rtts-assert/src/rtts_assert',
      types: true

What is this thing called AtScript I’ve heard of?

Further reading

You can read more details about the language constructs added in TypeScript (previously called AtScript because of some missing syntax in TypeScript that time) here.

Angular2 has no Controllers

It seems it got modern for the JavaScript MVW frameworks to drop controllers from their components (starting from Backbone.js). Instead of using controllers, Angular2 bet on component-based UI, similar to ReactJS. The core team dropped controllers but added components and kept the directives.

three different types of directives:

*out of date* > - Component is a directive which uses shadow DOM to create encapsulate visual behavior. Components are typically used to create UI widgets or to break up the application into smaller components. > - Only one component can be present per DOM element. > - Component's CSS selectors usually trigger on element names. (Best practice) > - Component has its own shadow view which is attached to the element as a Shadow DOM. > - Shadow view context is the component instance. (i.e. template expressions are evaluated against the component instance.) > - Viewport. According to the AngularJS docs, viewport is a directive which can control instantiation of child views which are then inserted into the DOM. (Examples are if and for.) > - Viewports can only be placed on <template> elements (or the short hand version which uses <element template> attribute.) > - Only one viewport can be present per DOM template element. > - The viewport is created over the template element. This is known as the ViewContainer. > Viewport can insert child views into the ViewContainer. The child views show up as siblings of the Viewport in the DOM. > - Decorator. According to the AngularJS docs (still incomplete) decorators are the simplest kind of directive is a decorator. Directives are usefull for encapsulating behavior. > - Multiple decorators can be placed on a single element. > - Decorators do not introduce new evaluation context. > - Decorators are registered through the @Decorator meta-data annotation.

Quick FAQ:

Doesn’t removal of the controllers violates the separation of concerns principle advocated by AngularJS?
Great question, Minko, thanks for asking! How given AngularJS application looks like? We have a view (a template), which is a composition of directives. These directives should handle the whole DOM logic. We also have services - they are responsible for encapsulating all the business logic. And we have controllers. The controllers are mostly user input handlers, they also add some properties to the scope. The best practices state that we need to keep the controllers as lean as possible. Let’s think of what we will lose if we move the user input handling and adding properties to the scope to our directive instead to the controllers. Can we reduce the code reuse? If we don’t create highly coherent directives - probably, if we couple the directives with the business logic this may happen (i.e. use domain specific service inside our dialog directive, for example). But what if we create a higher level directive, which is one or a fewer levels of abstraction above the primitives, which form our template? This way we handle the user input independently from our primitive UI components, so they are still completely reusable but we also remove one more component, which only makes the framework harder for learning.

Similar to React? Does that mean that we have to inline our markup inside the directives we define?
You can but you don’t have to. You can use inline templates or external files (just like using template and templateUrl in AngularJS 1.x).

Does that mean that I need to change the design of the whole app, i.e. turn each controller into a directive of type component?
No, you don’t have to change the design of your app. In order to make the transition even smoother you can use the “container component pattern” but also keep in mind that the new router.

Do I have to rewrite everything I already have?
Very likely to rewrite big parts of your application, but if you’ve structured your application properly (i.e. followed my style guide), you’d be able to completely reuse at least your services.

No Two-Way data-binding

One of the things AngularJS 1.x was loved about was the two-way data-binding using ng-model. Well, it is dropped from v2.0. Initially it might seems a bit weird, crazy and frustrating but it is actually a really good thing, do not be heartbroken. Removing the two-way data-binding leads to:

  • More explicit data-flow
  • No circular dependencies between bindings (so no TTL of the $digest)
  • Better performance
    • The digest loop could be run only once
    • We can create apps, which are friendly to immutable/observable models, which allows us to make further optimizations (for more information about immutable data take a look at my talk at ng-vegas or this great post by Victor Savkin, a core member of the AngularJS team)

Quick FAQ:

Does that mean that we’ll do a lot of manual work building forms?
No. Angular2 has a great forms module.

Single directional data flow…We can use Flux then?
Yes you can! I’d even recommend to use Flux! Here is one more great post by Victor Savkin about using Flux with AngularJS.

So Angular2 is basically ReactJS implemented by Google?
No. The binding mechanism is completely different. It provides wider functionality than React (Angular2 is lighter compared to AngularJS 1.x but still provides built-in directives, dependency injection, different components, etc.). This does not mean that you should give up using React and wait for Angular2, both frameworks have unidirectional data flow, which makes them suitable for the flux architecture. You might be able to make a smooth transition from React to Angular2 if you haven’t coupled the rest of your flux components (stores, actions, dispatcher) with your UI components.


What exactly is framework and what is a library? Lets take a look at AngularJS’ docs:

The impedance mismatch between dynamic applications and static documents is often solved with: a library - a collection of functions which are useful when writing web apps. Your code is in charge and it calls into the library when it sees fit. E.g., jQuery. frameworks - a particular implementation of a web application, where your code fills in the details. The framework is in charge and it calls into your code when it needs something app specific. E.g., durandal, ember, etc.

I wouldn’t call Angular2 a library but it is much closer to library rather than AngularJS 1.x. Anyway, what matters mostly is that it is on top of web standards. It uses shadow DOM for better encapsulation of the directives, takes advantage custom elements, etc.

Quick FAQ:

So I can’t use Angular2 in IE and any other browser which doesn’t support Web Components?
You can. There are a lot of polyfills, which handle the lack of support.

New Router

Brian Ford gave a talk about the new router of AngularJS. I’m not saying “the new router of Angular2” because it could be used in AngularJS 1.x apps as well, which will make your transition smoother. What is that great about the new router? It is more feature rich than the old ngRoute and with Angular2 in mind unlike uiRouter. Probably it is the only component, which got more complex to use (given the increased amount of features it has) but most likely it won’t be part of the core of the framework (similarly to ngRoute), given it is hosted in different repo.

You can use the new router inside your AngularJS 1.x app if you “emulate” the Angular2 component directive with the legacy controllers and templates.

Quick FAQ:

How I can try the new router?
You can use this repo.

Should I start my new project with the old router or the new one instead?
Use the new router.

Real Modules

During the AngularJS classes I led I had troubles explaining why AngularJS has modules, which must be loaded explicitly but there’s no way to load them asynchronously, without hacky solutions. Well, Angular2 uses the ES6 modules. Since they are not supported by the browsers yet, you can fallback to SystemJS and ES6-module loader, or transpile them to AMD, CommonJS or whatever you find suitable for yourself.

This allows creating bundles with the modules, which are required during the initial page load and loading all others on demand, asynchronously. That’s one of the things I’ve always dreamed of and I’m kind of disappointed it is added at this late stage.

PS: Here is a proposal concerning AngularJS 1.5, which allows asynchronously loading of components.

No more $scope

There are a lot of statements the $scope was a tricky for explanation concept to the AngularJS beginners. Well, I had harder times explaining the module system, anyway, there’s no such thing as $scope in Angular2! Again, there is no scope. Instead of binding to properties in the scope inside our templates, we directly bind to properties of our “components”.

For example, the component below has selector sample-app (i.e. we can use it as <sample-app></sample-app>) and template located inside ./templates/sample-app.html (you can find the whole source code at my GitHub repository).

  selector: 'sample-app',
  componentServices: [
  url: './templates/sample-app.html',
  directives: [Foreach]
class SampleApp {
  constructor() {
    this.names = NameList.get();
    this.newName = '';
  addName(newname) {
    newname.value = '';

We can directly bind to this.names inside our template, like this:

  <li *foreach="#name in names">{{name}}</li>

No scope at all! Awesome, isn’t it? So far, so good. We do not have scope. But remember, we used to use $scope.$apply in order to force execution of the $digest loop and perform dirty checking? How are we going to do this now? Well, we cant.

Quick FAQ:

I like the scope, I was able to explicitly state what I want to expose to my templates. Are there any advantages removing the scope except of “hard to explain to beginners”?
Some of the biggest memory leaks I’ve ever had were caused by forgetting to destroy the $scope of given directive. Removing scope leads to less AngularJS components, so less bugs, lower complexity. A lot of people were doing things which sometimes looked like workarounds, when inheriting the scope (thinking they’ve inherited the controller), doing complex publish/subscribe messaging between parent and child scopes etc. All these things will not be required anymore.

No more $scope.$apply

But how then AngularJS knows that anything outside it’s execution context has taken a place? Lets think where the changes might come from:

  • setTimeout
  • setInterval
  • prompt (yeah, there are people who still use it…)
  • XMLHttpRequest
  • WebSockets

All The Things

Basically a lot of browsers’ APIs. How we can be notified when the user invokes method from any of these APIs? Well…we can monkey patch all of them! That’s what Brian Ford explained in his talk about Zone.js in ng-conf 2014.

I bet now you’re thinking - “Oh God! Why I’d use something, which monkey patches all the browser APIs? This is just not right!”. Why it isn’t?

Quick FAQ:

Will patching the browser’s APIs lead to huge amount of bugs?
Very smart people, who know what they are doing, work on making Zone.js patch the APIs without any issues. It also has solid amount of tests.

Will using Zone.js slowdown the method executions?
According to the talk about Zone.js, this is not the case.

Errors in the Template Expressions

Another thing I didn’t really like in AngularJS 1.x was the lack of errors when you had a mistake inside an expression used in a template. The errors, which you were supposed to get were omitted and you weren’t aware that your code actually doesn’t work. Well, in Angular2 you will get runtime errors in such cases.


angular-translate was the default choice when it used to came to internationalization in AngularJS 1.x. It is a great tool, which allows you to define the different strings used inside your AngularJS application in json files and include them on the correct places using filters and directives. You are able to define different translations of these strings, using multiple json files for the languages you need. The language files are usually loaded on demand.

Since the AngularJS team has slightly broader vision for the way the i18n should be implemented they will add it as a project supported by Google. They will allow building the AngularJS templates with the correct strings embedded inside them. This will speedup the load time since you won’t need to load external files. AngularJS 1.4 has support for plurals and gender (which may ease the transition from 1.x to 2.0), in Angular2 will be implemented the string interpolation. For further information on the topic take a look at this video:

Quick FAQ:

Will angular-translate be still compatible with Angular2?
Most likely, no. I’m not aware whether the angular-translate team have plans to port it to the new version of the framework.

Ultra Fast Change Detection

There is still no final version of the change detection. The underlaying implementation should not concern us, the AngularJS team will do the best based on huge amount of benchmarks, on different devices in different environment. This section is only for fun, exploring some design decisions.

Another completely innovative idea I found, digging inside AngularJS’ source code was inside the JITChangeDetector. Mostly because of the inline-caches, the JavaScript VMs are capable of doing smarter optimizations in expressions like:

this.value === oldValue;

The AngularJS team decided that they can generate JavaScript classes, which implement this change detection mechanism, instead of using method calls (take a look at these benchmarks). How does it work? According to my quick research:

  • AngularJS tokenizes the registered (“watched”) expressions
  • AngularJS builds AST
  • Using the visitor pattern AngularJS’ creates the so-called “ProtoRecords” list.
  • Based on a template and the ProtoRecords, AngularJS implements the “dummy” change detection for a specific component.

Quick FAQ:

Does it mean that the generation of source code will slowdown the execution of my app?
It is done when the bindings change, lazily. Probably it will perform better in most scenarios.

Is it going to be hard for debugging?
We trust AngularJS that it is going to be implemented well and we won’t need to touch it!

Will it lead to any debugging complications (for example entering the change detection, generated class because of a breakpoint we’re in)?
If you use your debugger properly you should not have any issues. Take a look at the slides of Addy Osmani on the state of DevTools, 2015, jQueryUK.

Further reading

For more information you can take a look at the design docs (here and here) and the AngularJS’ source code.

It is not production ready

The API of Angular2 is still under development. There are a lot of things, which are still not clarified (like change detection, best API, forms API, etc.). You can play with the framework using the quick start or my seed project

What else we have left?


According to the documentation, Angular2 will have formatters pipes, which are equivalent (a bit more powerful, since allow enhancement of the change detection) to the filters, well known from version 1.x.

Improved DI

The dependency injection mechanism will be used with the decorators syntax provided by TypeScript. You can take a look at the source code here. Since it is implemented as external library, you can use it inside your project. Here is a simple example from the git repo of di.js:

import {Inject} from 'di';
import {Electricity} from './electricity';

export class Fridge {
  constructor(electricity) {
    this.electricity = electricity;

  getEggs() {
    return '3 eggs';


Angular2 will be a brand new framework, which is not backward compatible with AngularJS 1.x. It is implemented in TypeScript but you don’t have to use it if you don’t want to. It implements some of the ideas from ReactJS, mostly the unidirectional data flow, which makes it work great with the flux architecture. It is on top of web standards (which is a big bonus compared to ReactJS) and takes advantage of some of the web components’ APIs. It will be much faster and lighter compared to AngularJS 1.x and will be supported by the modern browsers with polyfills for older ones (as far as I know the support for IE7 and IE8 will be dropped).

You can use some of the libraries used for the development of Angular2 (like DI, rtts_assert, router, benchpress) in your current AngularJS and non-AngularJS projects.

Should I use it in production now? No, but you can experiment with it. If you are planning to start a new project with AngularJS, better use AngularJS 1.x instead. Following some practices mentioned above will make your transition easier.