i appreciate the author's effort but don't feel like i have a better handle on the applicability of each framework to real projects (like many similar articles)

i appreciate the author's effort but don't feel like i have a better handle on the applicability of each framework to real projects (like many similar articles). basically, this article lists some good and bad features of each framework with some light commentary about a few of those features, which means it doesn't really help you answer the question implied by the title ("which js framework should you choose?"). i think it might be better to use a non-trivial example and show side-by-side implementations for 10 or so important aspects (routing, templating, data binding, etc.), with commentary on what kinds of projects would benefit the most from each frameworks' approach to each aspect. since airpair is about selling programming expertise, this would demonstrate actual expertise that would be attractive to prospective customers (vs. the ability to talk about programming, which is easier).