When comparing JSLint vs Sublime Linter, the Slant community recommends Sublime Linter for most people. In the question“What are the best plugins for Sublime Text?” Sublime Linter is ranked 8th while JSLint is ranked 18th.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Enforces a very high standard
Since it's relatively old (it was made in 2002) and made by Douglas Crockford, considered a JavaScript God by many JavaScript programmers. It was created to enforce what in Crockford's experience are the good parts of JavaScript. This means that it's considered by many the best way to enforce the highest standards in JavaScript.
Pro No setup required
JSLint comes preconfigured and ready to be used.
Pro Helps you find errors in the code
Pro Supports pretty much every language
Cons
Con Highly opinionated
JSLint has a very strict, dogmatic ruleset that cannot be changed or warnings turned off. So much so that rarely any code will pass JSLint tests. It's reasonable to evaluate if all warning are worth changing.
Con Difficult to know which rule is causing which error
Since you can't edit the rules and it's not programmed in a way to display the rule that's being broken, it's difficult to understand which rule has been broken.
Con No way to support ESnext
Con Tends to cause Sublime Text to run slowly
With Sublime Linter installed, dialog boxes warning that the plugin is running slowly can become a common occurrence, depending on the types of files you regularly work with.
Con Many default linters require installing Node.js
Javascript, CoffeeScript, and even the CSS linter require installing Node.js to function