Another one of those articles :-) The author feels the pulse of a javascript framework's culture. Watches versions, core developers and his own feelings about i

Another one of those articles :-) The author feels the pulse of a javascript framework's culture. Watches versions, core developers and his own feelings about it all. Career opportunities and sunk learning costs are at stake. As everyone is learning, no project is really "typical" and so much is up to personal taste, chances are we won't see a case study of a project in various stages. Ideally the author of such a study would describe clearly just when the framework clicked for him, and when it became a burden. Just what code is so cumbersome it's never fun to work with? What feature was rejected due to performance concerns? All we can do is read those articles and, going meta, keep track of the frequency and sigificance of these articles and get an idea where the hype train is going...