CommentComment

The problem with Angular. Wait, there's a problem?

As many of you know from this newsletter, I'm building in an app in Backbone. I consciously chose Backbone over Angular because I had already had Backbone exposure, and after some basic research, Angular felt over-baked for me. Part of me love(d/s) some things, like the mark-up ng attributes, but I wasn't sold. I really found The problem with Angular article below interesting, whether it's to feel better about my current Js front-end path, or because Peter-Paul makes some great points.

Galen Vinter

Opinions

Learning



Resources


Responsive

News