When comparing GoSublime vs JSHint, the Slant community recommends GoSublime for most people. In the question“What are the best plugins for Sublime Text?” GoSublime is ranked 10th while JSHint is ranked 35th. The most important reason people chose GoSublime is:
* code completion from Gocode * context aware snippets via the code-completion popup to complement the existing SublimeText Go package. * sublime build system(ctrl+b) integrating with GoSublime 9o command prompt * lint/syntax check as you type * quickly jump to any syntax error reported (and jump back to where you were before (across files)) * quickly fmt your source or automatically on save to conform with the Go standards * easily create a new go file and run it without needing to save it first (9o replay) * share your snippets (anything in the loaded file) on play.golang.org * list declarations in the current file * automatically add/remove package imports * quickly jump your import section(automatically goes to the last import) where you can easily edit the pkg alias and return to where you were before * go to definition of a package function or constant, etc. * show the source(and thus documentation) of a variable without needing to change views
Ranked in these QuestionsQuestion Ranking
Pros
Pro Provides code completion and other IDE-like features
- code completion from Gocode
- context aware snippets via the code-completion popup to complement the existing SublimeText Go package.
- sublime build system(ctrl+b) integrating with GoSublime 9o command prompt
- lint/syntax check as you type
- quickly jump to any syntax error reported (and jump back to where you were before (across files))
- quickly fmt your source or automatically on save to conform with the Go standards
- easily create a new go file and run it without needing to save it first (9o replay)
- share your snippets (anything in the loaded file) on play.golang.org
- list declarations in the current file
- automatically add/remove package imports
- quickly jump your import section(automatically goes to the last import) where you can easily edit the pkg alias and return to where you were before
- go to definition of a package function or constant, etc.
- show the source(and thus documentation) of a variable without needing to change views
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.
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.