<story><title>Throne of JS: Eight JavaScript MV* Libraries Compared</title><url>http://blog.stevensanderson.com/2012/08/01/rich-javascript-applications-the-seven-frameworks-throne-of-js-2012</url></story><parent_chain></parent_chain><comment><author>Maciek416</author><text>I attended the conference, and the topic (framework vs. framework vs. library) was definitely timely. There are strong points of contention between the major competing frameworks/libraries right now, and this was reflected in the panel discussions.&lt;p&gt;What struck me about the talks I saw was the degree to which each project strongly reflects the personalities of its authors; Jeremy Ashkenas was indeed (as the article says) the calm zen master of the panels, taking a minimally-prescriptive stance on how his code should shape your code.&lt;p&gt;Tom Dale and Yehuda Katz, on the other hand, came in with passionate arguments for the idea that JS frameworks should have strong opinions and exert a great deal of influence on your code and the outcome of your solutions. Katz&apos;s central thesis seemed to be that for highly common problems for which Ember would be used, extremely similar (if not identical) solutions should emerge.&lt;p&gt;All in all a good conference, and very differently-flavoured from JSConf.</text></comment>
<story><title>Throne of JS: Eight JavaScript MV* Libraries Compared</title><url>http://blog.stevensanderson.com/2012/08/01/rich-javascript-applications-the-seven-frameworks-throne-of-js-2012</url></story><parent_chain></parent_chain><comment><author>ilaksh</author><text>&lt;a href=&quot;http://tjholowaychuk.com/post/27984551477/components&quot; rel=&quot;nofollow&quot;&gt;http://tjholowaychuk.com/post/27984551477/components&lt;/a&gt;&lt;p&gt;Those frameworks are great, but they all fail to take advantage of a key advance in software development: the widget.&lt;p&gt;Reusable, composable GUI components that package front end and back end files together and can be distributed easily as plugins are the next step up in abstraction and superior from a software engineering perspective.&lt;p&gt;The reason many web developers aren&apos;t able to either grasp or accept that is because A) understanding and building those types of components that are truly generic enough to be applicable to a wide variety of applications as well as reusable, has a significant learning curve and is time consuming and B) the better you are at it, the less likely you are to get credit for your programming skills, because unfortunately if you can build an application without typing colorful ASCII text, then you didn&apos;t do any programming and aren&apos;t a programmer.&lt;p&gt;To get past B) we just need to redefine what programming is, and also grow up a little.  Also realize that even if you are programming with GUI components, you still have to create new components sometimes, so you are still programming and still a programmer.&lt;p&gt;I have a very early rough draft system that I am throwing together on my own, mostly because very few people seem to be able to appreciate these concepts.  Or the ones that do are happy to use existing systems like ASP.NET or WordPress.&lt;p&gt;&lt;a href=&quot;https://github.com/ithkuil/cureblog&quot; rel=&quot;nofollow&quot;&gt;https://github.com/ithkuil/cureblog&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://vimeo.com/43784316&quot; rel=&quot;nofollow&quot;&gt;https://vimeo.com/43784316&lt;/a&gt;  Note that I have modernized the interface somewhat since I made that video.</text></comment>