> @izs - I think you overreach by grouping him as anti-semi-colon [sic]. Those are your words, not mine. The "other side", as I put it, isn't necessarily anti-

> @izs - I think you overreach by grouping him as anti-semi-colon [sic]. Those are your words, not mine. The "other side", as I put it, isn't necessarily anti-semicolon. To be on the other side of this particular argument, they merely have to disagree with the assertion that a semicolon at the end of the statement is a must, and not a style choice. And izs did choose that style for npm. > Thomas Fuchs - heard of him, he's done lots of stuff JavaScript and PHP wise. I'll give you that one. He gave us Scriptaculous, and some decent PHP resources (like PHPatterns, IIRC). He's active in Rails. There's Zepto.js too, and he was a longtime core member on the Prototype JavaScript framework. He's influential. > The main reason the quality of JavaScript has increased dramatically in the last 6 or 7 years has been because of a coalescing towards a JavaScript best practice. This has mainly been led by Douglas Crockford and JavaScript developers at Yahoo. I strongly disagree. The driving force was the increase in importance of the JavaScript language. He was part of that trend. He helped speed it up, but it would have happened regardless. > JS Lint is the starting point for this improved use of JavaScript. JS Lint is a starting point. There are other valid starting points. > And I guess that's the real problem here. Not using JSLint before using JSMin. But @fat isn't using jsmin. And there are great alternatives, so this is a valid choice! > What would "JavaScript the Railified Parts" look like side-by-side with Crockford's The Good Parts, and Flanagan's Definitive Guide? It would look like this: http://pragprog.com/book/tbcoffee/coffeescript http://pragprog.com/book/tbcoffee/coffeescript