Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariJSLint vs FileDiffs
When comparing JSLint vs FileDiffs, the Slant community recommends JSLint for most people. In the question“What are the best plugins for Sublime Text?” JSLint is ranked 18th while FileDiffs is ranked 39th. The most important reason people chose JSLint is:
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.
Question Ranking
Pros
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.
Pro Allows you to open diffs in external diff tool
Instead of creating a new tab with the diff in it, you can tell FileDiffs to open the diff in an external diff tool for side by side comparison and other features.
Pro Easily compare arbitrary code sections
FileDiffs allows you to compare any arbitrary text through multiple commands:
- Compare the current file or selection with any other file via a file select menu
- Compare the current file or selection file with previously selected tab or window or panel
- Compare the current file or selection with your clipboard
- Compare between two selections through Sublime Text's multi-select feature
Pro Command pallet integration
In addition to providing shortcut commands for custom shortcuts, FileDiffs adds new command pallet entries. If you don't use diffs often enough to warrant memorizing a new shortcut command, the command pallet provides a quick and easy way to access the plugin.
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.
Con No way to support ESnext
Con Doesn't have side by side comparison
After running FileDiffs, it creates a new diff file in a new tab, which doesn't have the benefit of showing the diffs in context. However, it is possible to open the diff in an external diff tool instead of creating a new tab.
