I’ve always been fond of keeping an eye on the horizon, to watch what new technologies will emerge, and what useful tools we will have in the years to come. With this mindset I recently started a quest to learn Angular 2, before it will be mainstream. I had studied it a bit earlier, too, but then it felt way too ugly and early to have anything to do with project work. Working for Solita - there is no excuse to let your skills or knowledge go stagnant, or letting your toolbox to be outdated. So I went looking for Angular 2 - but ended up finding something else.
What is Aurelia?
Aurelia is a framework that is relatively new and not many have heard of it - or used it. It’s not stable for production use yet - but it is looking pretty good already. It’s also looking a lot like Angular 2, just much better. This is of course no big surprise, since one of the key developers is Rob Eisenberg, previously a member of the Angular 2 team.
What’s cool about Aurelia?
What fascinates me about Aurelia? Many things. One core thing is that it’s based on using ECMAScript 6 - and 7. This means you are able to code with future languages - right now. But it still works in todays browser, thanks to Babel 6to5 transpiler that forms a core part of this framework. This means support for all current Evergreen browsers, and there’s even some work being done for IE10 and IE9 support. It’s beautiful, and applicable today.
Don’t believe me? Take a look at this:
What is happening here? A lot. Aurelia uses ES6 module system so import becomes much simpler than with Angular+RequireJS combination. We see dependency injection in action, we provide some metadata and HttpClient becomes injected in our constructor. And no more $scope! Our scope is now the viewmodel, and we simply store any interesting variables in this (that now works better, too)
How’s the view?
Aurelia uses view-viewmodel architecture, and what we see here is a viewmodel named App. The view for this viewmodel would be named app.html, and it looks like this:
Here we can see an example of another powerful Aurelia feature - binding. There’s a whole binding engine at work to figure out what’s the best way to implement the binding based on your code. There are several options. Any html attribute may be bound, in this case you can see repeat.for, but similarly you can bind with
href.bind="somehref" - you can also use one-way binds or two-way binds by replacing
.bind part with
.two-way, to be more precise.
To me it seems like Aurelia is very clean and pure code, compared to the mess that Angular 1 and 2 very easily tend to become. Using strong points of ES6 is definitely a plus, since ECMAScript 6 will come, one day. Starting the transition now will be valuable for me.
What else is there?
So, other impressive things about aurelia are:
- It’s backed by Durandal Inc - not just a one guy project
- It’s highly modular - you can pick which modules you like and drop the rest
- While you can use ECMAScript 5, CoffeeScript, or TypeScript, you probably like to use ES6
- While you can use bower and grunt, you probably want to use jspm and gulp instead
- There are conventions over configuration - for example, to create a new view, you just create view.js and view.html file - and you don’t need to configure anywhere how they work together - it’s just magic. I like magic (well, good kind of).
- You can use existing libraries easily with your solution, I used Bootstrap and Underscore in this little tech demo of mine.
- Routing - yeah, there’s much improved routing capabilities, much effected by work done for Angular 2
- Custom elements and templates
- This framework didn’t appear from scratch - it’s based on Durandal, as well as earlier 6to5 transpiler system, and of course Angular 2 work. That means certain level of maturity even though it’s very new.
Time to wrap it