I've been having a hard time getting excited about Web Components. I mean, I'm pretty sure I get why they're useful and I expect to be using them a lot in the future. It's just that I haven't been able to see Web Components as the "tectonic shift" people make them out to be.
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.
This article addresses the dependency injector of Angular 1.x, which is the version everyone is currently using. The 2.0 version will be very different, and is an interesting topic in its own right. I've written a bit about it earlier.
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.