Git Gutter vs JSLint
When comparing Git Gutter vs JSLint, the Slant community recommends Git Gutter for most people. In the question“What are the best plugins for Sublime Text?” Git Gutter is ranked 7th while JSLint is ranked 18th.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Makes it really easy to see if a line has been inserted, modified or deleted.
Pro Has hot keys for jumping to the next changed line in the file
Git Gutter exposes the commands git_gutter_next_change
and git_gutter_prev_change
for navigating to parts of the file that are different from git. By default they're bound to ctrl+shift+alt+j
and ctrl+shift+alt+k
respectively, but you can change them in your user key bindings file.
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 Directory locking causes issues when changing branches
If you have Sublime Text 3 open when switching branches directories are not removed if they are specific to a branch. This can create a real mess as the directory is treated as a new addition to the destination branch. Deleting the directory is still seen as a directory added then removed in the branch.
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.