December 22, 2014 in
As far as I can tell, it started with Backbone, moved onto things like Knockout,Ember and of course, Angular.
These days though? I’m not so sure.
Over the last year, I’ve built a couple of one page applications that made fairly extensive use of Angular.js, and after a steep learning curve, I’m now fairly comfortable with all of its ins and outs. With the benefit of hindsight I wonder what benefits it actually brought to the table beyond library lock-in.
Off the top of my head, I could argue that Angular provides:
What’s my point? Well, as a blog post goes, this is more of a brain-dump of random thoughts that I’ve had over the last few months around the eco-system rather than a logically stringent argument. But the conclusion that is starting to form in my head is that the big all-singing, all-dancing frameworks will give way for smaller, more focused libraries, in some cases the same old libraries we used before the big frameworks came round. Just like for so many other languages and eco-systems, it is slowly dawning that small is beautiful and big monolithic frameworks are more pain than they are worth - be clear about your requirements and pick small libraries that fit them.