#Why People Hate Your Framework
##Abstract
Today's JavaScript community suffers from a divide. On one side of the divide are those people who praise npm's module system over all else, eschew even the most micro of frameworks, loathe CoffeeScript and demand that promises get off their respective lawns. On the other are those which yearn for the "rails of node", write everything in CoffeeScript, love Angular to pieces and extoll the virtues of promises at every opportunity.
Having been involved in the node.js community for some time, and having talked shop with some of today's foremost JavaScript philosophers, I've began to develop a theory explaining the root causes of this divide, the truth behind both extremes in position, and how best to balance the concerns of both forces.
##Speaker Bio
In late 2010, as I was in grad school for an engineering degree tangentially related to software at best, @substack showed me this newfangled platform for writing webservers called node.js and insisted that it was way better than MATLAB. Within a year I had ditched engineering and moved from Alaska to the Bay Area to go on a JavaScript adventure.
While there, I began working for Nodejitsu and dived into supporting their public cloud, maintaining and contributing to Flatiron, and learning how to write software that only crashed when it was supposed to. I've also hacked on the Big framework, wrote one of the more popular static fileserving libraries for node, and inadvertently trolled everybody that's ever published to npm. Now, I'm working at i.TV in sunny Utah, learning a whole new stack of libraries and reflecting on all my javascript experiences thus far.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。