When comparing GoSublime vs JSLint, the Slant community recommends GoSublime for most people. In the question“What are the best plugins for Sublime Text?” GoSublime is ranked 10th while JSLint is ranked 18th. 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 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.
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.