That's exactly my problem. I don't have any issue with removing semi-colons, using comma-first style, using == instead of ===, removing brackets if (name) return "hey" Since I know how it works. Even if I make a mistake, I find it fast.
The problems begins with bs/ms students coming for a short project. They don't have time to properly understand and learn JS, so they immediately start to write code. I often see them fighting with the bugs that linter would spot immediately. So I decided for my own projects to use the light style but for the projects with students to use jshint, because if they start to follow my style they start to have problems because of language ignorance. On Friday, February 24, 2012 9:34:03 PM UTC+1, Naouak wrote: > > at yui conf this year, Cockfod explained why he did JSLint and how. These > rules emanes directly from most recuring errors he founds on newsgroups. > > As these may seems eally harsh, JSLint is a good tool to find unsuspected > bug or strange bug. > > As I'm often thinking: rules are made for those who cannot think and go > beyond. Before, saying that a rule is bullshit, try to understand why it's > there and learn from it. > >> -- 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
