jslint

I put mootools and jquery through jslint.com and jslint found so many things it didn't like that I wonder if the cristicism is indeed valid.

Doug has never said that code which fails JSLint is obviously retarded, or written by fools.

The best part of this guide is that they included a eslint and jslint rules file.

If you want more control, use ESlint or jslint or jshint and define your own rules.

Absolutely, to be fair to JS, Eich admitted it was an horrible mistake, and tools like JSlint enforce the use of ===.

I see the bug as JSLint's problem, not the code in question (though admittedly that was bad code).

It's not related to performance exactly, but it will run your JS through jslint, minify, beautify it (if it's in a gnarly style).

I was hoping for something completely web-based, like jslint.com, but which would reflect IE's javascript engine and error console.

This is a very big deal for JavaScript developers because it is like having JSLint, YUI Compressor, and Chuck Norris rolled into one.

I should check jshint but unfortunately jslint primed me against that kind of tools.

The build environment has jslint set up in it too.

If this is your preference, JSLint has you covered.

You can easily dismiss the numerous non-style related errors that JSLint finds because of the claim that JSLint "opinionated".

I wonder what this means for Douglas Crockford's "Good parts" subset and JSLint?

Maybe we need to start proselytizing and make all the incoming Javascripters repeat: "There is no god but Crockford, and JSLint is his prophet."