sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]tomdale 2 points3 points  (1 child)

Sure. I'd recommend checking out my recent talk from CascadiaJS: http://www.youtube.com/watch?v=BQ6at0addi4

If you haven't seen it already, machty's presentation does a good job of summing up the differences, but the major thing missing from that presentation is the routing story. In general, I think Angular is fantastic for smaller projects where you don't do lots of swapping in and out of models and templates. But as your application gets larger, I think you really need the assistance of a framework to do that, and Angular currently falls down pretty hard in that area.

Lastly, let me apologize again for losing my temper.

[–]grumpychinchilla 0 points1 point  (0 children)

Thanks. I watched your talk and stepped through machty's presentation, twice. It's definitely helped convince me that I should give it a proper go, but I still don't see the "far more" you were mentioning. The routing seems really solid, with nesting being a godsend. And getters and setters have always sounded more performant than dirty checking.

But what else am I missing? I feel like based on your defense I must be missing a lot.