JSHint vs sublimious
When comparing JSHint vs sublimious, the Slant community recommends sublimious for most people. In the question“What are the best plugins for Sublime Text?” sublimious is ranked 30th while JSHint is ranked 35th. The most important reason people chose sublimious is:
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.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Customizable ruleset
Since it's creation, JSHint was created to be a more configurable version of JSLint (it's actually a fork of JSLint itself). Every rule is configurable through a configuration file.
Pro Comes with support for many librariers
JSHint supports libraries like QUnit, NodeJS, jQuery, Mocha out of the box.
Pro Basic ES6 support
Basic ES6 support is included.
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 No way to support ESnext
There's no support for ESnext available.
Con Difficult to know which rule is causing an error
Because it does not display the rule name that is being broken, it's difficult to know which rule is actually causing the error.