Todd Motto

I've been working pretty much exclusively with Angular for the past 18 months on some high volume financial processing systems. Shipped 3 codebases that would probably be considered 'large'. It's been one of the best development experiences I've ever had. The learning curve is steep, but when you get into the groove, when it finally clicks, then you can really take off with it. I love the tooling (node, Yeoman, Grunt, jshint, karma, protractor etc.). While not perfect, it's definitely helped me write better, more readable code. The one article that helped me get to my 'gotcha' stage was this one by Todd Motto: http://toddmotto.com/rethinking-angular-js-controllers/

Wow, great idea. I wish this was available as a npm package. A couple of things, sometimes the service doesn't work and returns "YUI Compressor : 0bytes (100%)" or "JSMin : 886bytes (0%)". A typo: succees. The references section could be expanded with resources about writing JS code in a way that enables optimizations: http://toddmotto.com/what-function-window-document-undefined-iife-real… https://curiosity-driven.org/minimal-loader

Another compelling argument for the same position: https://toddmotto.com/deprecating-the-switch-statement-for-object-lite…

It's pretty simple with modern tools. For example, I'm learning Angular at the moment. I needed to learn how to use an IF statement in the HTML code. The first google result is a blog post [1] from some guy. It's helpful, but really dilutes the core material. So instead I just went directly to the angular docs [2]. This was straightforward and gave me the info I needed to know. Now CLI manuals from tools created in the 80's and 90's? Those are trickier. I'm still trying to learn a good way to grok those tools, but so far blog posts and Stack Overflow have been better than the man files, in my experience. [1] https://toddmotto.com/angular-ngif-else-then [2] https://angular.io/api/common/NgIf

Yea, no, just read this: https://toddmotto.com/mastering-the-module-pattern/ And you will never use it unless you are writing a library because Angular/React/Vue do it for you.

One thing that definitely can be improved is using "Controller As" syntax. It solves most of the $scope issues. Here's a good writeup: http://toddmotto.com/digging-into-angulars-controller-as-syntax/

> Yes, a prerequisite to using a JavaScript framework is understanding prototypical inheritance Obviously, but you shouldn't have to care about prototypical inheritance for simple databinding. The way view-models work in Angular leads to some complicated scenarios which, in my opinion, shouldn't exist in the first place (http://toddmotto.com/all-about-angulars-emit-broadcast-on-publish-subs… > What? See https://medium.com/@kentcdodds/counting-angularjs-watchers-11c5134dc2e… for an explanation. > To date I haven't seen a coherent argument against Angular; complaints seem focused around having to learn framework specific syntax (present in any large MVC framework) or the perceived "heaviness" of the framework (suggesting the apps you're building aren't complex enough to justify something like Angular) I have no problem with learning framework specific syntax and Angular is actually lightweight, both from an architecture and from a code weight point of view. What I do find problematic in Angular are some design decisions which often lead to complicated, and non-beautiful, code. Angular is no doubt incredibly useful, even for smaller apps, and I'm grateful for its existence. It is a step in the right direction. But I do think it has room for improvement.