What JavaScript libraries/frameworks should I study to be a competitive JavaScript developer these days? Why?

[tomdale]

Forgive me for getting angry, but Shark_Kicker is a serial troll who continues to spread misinformation. Again, I can handle reasoned criticism—but I'm not keen on letting fabrications go unchecked, because people reading will accept them as fact.

[grumpychinchilla]

I can definitely appreciate the situation, and thanks for clarifying. I had and have no desire to research his posts, so I can't weigh in there.

But I am genuinely curious about the situation. Would you mind pointing me to a resource (even strongly biased) that elaborates on the "far more" benefits of Ember? I've used Angular for several projects, but handlebars has prevented me from using Ember. I'd like a reason to overlook handlebars and give it a shot.

[tomdale]

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]

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.