Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariJSLint vs sublimious
When comparing JSLint vs sublimious, the Slant community recommends JSLint for most people. In the question“What are the best plugins for Sublime Text?” JSLint is ranked 18th while sublimious is ranked 30th. The most important reason people chose JSLint is:
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.
Question 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 Pre-configured with layers
Whenever you need to work on a new language that you don't have plugins for yet, you can choose to check if sublimious has a layer for that language. If it does, all you need to do is activate it and sublimious will automatically download all plugins you need for that language, add keybindings for efficient usage and set the optimal settings for these plugins.
Pro VIM centric
This plugin is perfect for VIM fanatics. It tries to add VIM keybindings to everything, even to where you didn't know it was possible like the sublime text overlay or the sidebar
Pro Ergonomic shortcuts
sublimious adds shortcuts that actually make sense. "p f" for example searches files in the current project. "g s" executes "git status" and so on, you get the idea. It even comes with a helper that shows you what shortcuts are available.
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
