Douglas Crockford might be opinionated - and Anton Kovalyov and Paul Irish are fantastic fellows - but a fork of JSLint reminds me of the South Park premise: if you allow one episode to be censored then you in the end everything will have grounds for censorship... the fork looks all dandy now - as long as "the community" doesn't end up having too much say in the matter. It's a pretty dang big community we've got now…
JSHint: An Community Driven Fork of JSLint
21–30 of 30 posts
Re: JSHint: An Community Driven Fork of JSLint
#22According to the JSHint website it is "an open-source project that is supported and maintained by the JavaScript developer community.". However, the license still contains the following clause: "The Software shall be used for Good, not Evil." So it is not using an OSI approved license, and a such I would not consider it open source. That clause adds a restriction on how you can use the software, and a very vague rest…
"I give permission for IBM, its customers, partners, and minions, to use JSLint for evil."
Previously posted on HN source: http://wonko.com/post/jsmin-isnt-welcome-on-google-code
Re: JSHint: An Community Driven Fork of JSLint
#23Re: JSHint: An Community Driven Fork of JSLint
#24Earlier quoted context omitted.
It's concerned about the declaration of i within the loop's first term. Since JavaScript only has function-level scope, that variable leaks into the broader context, which can lead to unexpected behavior.
Not if you actually, you know, know what you're doing. This dumbing down of programming does not work--if you have clueless people working on code, it'll end up broken, no matter how many tool-enforced 'best practices' they follow.
Re: JSHint: An Community Driven Fork of JSLint
#25Earlier quoted context omitted.
It's concerned about the declaration of i within the loop's first term. Since JavaScript only has function-level scope, that variable leaks into the broader context, which can lead to unexpected behavior.
Not if you actually, you know, know what you're doing. This dumbing down of programming does not work--if you have clueless people working on code, it'll end up broken, no matter how many tool-enforced 'best practices' they follow.
Re: JSHint: An Community Driven Fork of JSLint
#26The snarky comment seems unnecessary, "The most important difference is that JSHint is developed and supported by the JavaScript developer community and not by one very opinionated person". Douglas Crockford did a lot of great things for the JavaScript community. Considering they had just forked this, I'm not sure how they can immediately claim that theirs is supported by the JavaScript community, while JSLint is sup…
Crock's contributions are massive, I agree. I'm so glad that we've had a JSLint in the first place. However, JSLint has gotten increasingly more opinionated in the past few months.. For example, the standard for loop: `for (var i = 0, len = arr.length; i A lot of these sorts of changes don't have flags to customize, so that's something that JSHint aims to fix. Start with some great defaults, and allow them to be cust…
Re: JSHint: An Community Driven Fork of JSLint
#27Why are they forking jslint instead of modifying Google's Closure lint? ( http://news.ycombinator.com/item?id=1654082 ). Google's code has a more true open source license.