Much has been written about Angular's dependency injection framework. As I've been recently writing the dependency injection chapters of Build Your Own AngularJS, I thought I might as well join the club and provide my own introduction to Angular DI...
The CraftConf conference has me back in Budapest for some industrial strength geekery, and what a conference it is! The speaker lineup is what originally attracted me here and it certainly hasn't disappointed. But everything else has just worked as well: The venue is fantastic, the Wifi uncharacteristically functional, the pacing of the schedule just right and the coffee in between sessions good. Kudos to the organizers!
Here's a hopefully semi-cohesive summary of some of the talks I attended today.
I like how these components are being developed as independent modules in independent repositories. This makes it possible for app developers to mix and match Angular libraries with other frameworks and tools, whereas Angular 1.x has been much more of an all-or-nothing proposition.
One of the new components I find most interesting is the dependency injection library at angular/di.js. It is the library that will power dependency injection in Angular 2.0, but it is also a standalone DI framework that can be used in non-Angular contexts, enabling some of that mixing and matching.
I've been playing around with AngularDart, the up-and-coming Dart web framework from the Angular team. Not only because we have a Dart Flight School event in Espoo this weekend, but also because it's an interesting piece of technology to me as an AngularJS developer: Many of the ideas and features that will eventually ship with AngularJS 2.0 are already in AngularDart today.
In this article I'll talk about a few of the observations I've made about AngularDart, mainly comparing it to AngularJS. For a prior article about similar subjects, do take a look at Victor Savkin's excellent "AngularDart for AngularJS Developers".