Crockford himself writes "JSLint will hurt your feelings". We don't need to discuss what style is the best, it's the same as discussing "the best programming language". You can't fight about anyone's taste.
JSLint is especially good if you have a problem in you code and can't find it. JSLint will give you some possible problem sources. If you want to run a Lint check on filechanges or precommit, I recommend JSHint, a community driven fork of JSLint with more options for specific styles of coding. Am 20.02.2012 16:34, schrieb Dave Clements: > personally I think there's safety in JSLint, Crockford's experience > and research have led him to the conclusions he's made for the JSLint > rules, his decisions are less about style (i.e. what looks nice to > me), and more about the minimization of human error with clearer > expression of programmer intentions within code for the purposes of > collaboration. > > Having said that, there's always room for improvement but > "improvement" has to be strictly confined to what JSLint does > (minimization of human error etc), and not what looks to me. > > > Dave > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
