JSHint vs Sublimerge
When comparing JSHint vs Sublimerge, the Slant community recommends Sublimerge for most people. In the question“What are the best plugins for Sublime Text?” Sublimerge is ranked 26th while JSHint is ranked 35th.
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 Three-way diff allows easy merging of files
Pro sublimerge
i recommend Sublimerge
Pro Highlights intraline changes
Pro Built-in support for Git, Subversion and Mercurial commands
Sublimerge automatically integrates with your version control history, and lets you compare between revisions, branches, remotes, and the staging area.
Pro Can compare to clipboard contents
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.
Con Bad tech support
Con It's NOT Open Source
You can't fix or, implement nothing. And when the developer abandons the project you will be left in the lurch.
Con It's not free
Nither as free price nor as free in freedom.
Con Cannot compare text within the same file
Sublimerge can only compare entire file diffs, but not two selections within a file. Comparing within files can be useful for example, by refactoring two similar functions to use a shared function. With Sublimerge, you need to copy the sections into two new temporary tabs and compare between the two. This can be cumbersome, as if you have another untitled file, you won't be able to know which one is which.