I kind of can't believe he called Angular easy to learn. One of the most common things you hear about it is the steep learning curve, which is not helped by the docs (the skimpiness of which is another frequent lament). In my experience Angular is learned by Googling problems you have, which are then explained in Stack Overflow posts.
As an aside - this is something I've hardped on before, but I just really think it is not helpful to anyone to use examples whose names are so abstract:
This is meant as an example of something you should not do. But it's nonsense - it's quotes and semicolons separated by meaningless names. Of course that is the point, but in turn that is my point - give a better example, one that models something one may do in the real world but should not, so that the person reading the example actually understands what not to do. Instead of that, something like this:
ng-click="shoppingCartId = 52; initCart(52); var myShop = new Shop();"
People know what shopping carts are. "shazbot" and "nanoo nanoo" are whimsical references to an old sitcom. Entertaining to the author, perhaps, but not helpful.
As an aside - this is something I've hardped on before, but I just really think it is not helpful to anyone to use examples whose names are so abstract:
This is meant as an example of something you should not do. But it's nonsense - it's quotes and semicolons separated by meaningless names. Of course that is the point, but in turn that is my point - give a better example, one that models something one may do in the real world but should not, so that the person reading the example actually understands what not to do. Instead of that, something like this: People know what shopping carts are. "shazbot" and "nanoo nanoo" are whimsical references to an old sitcom. Entertaining to the author, perhaps, but not helpful.