When comparing JSCS vs JSHint, the Slant community recommends JSHint for most people. In the question“What are the best JavaScript linting tools?” JSHint is ranked 2nd while JSCS is ranked 3rd. The most important reason people chose JSHint is:
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.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Support for custom reporters
JSCS supports custom reporters, which are very helpful when you want to integrate JSCS with other tools that require a specific writing style.
Pro Several presets available
JSCS needs a configuration file and a preset to start linting your code. But it's not a problem since there are a lot of pre-made presets available in their website. jQuery style, and Google coding style for example are included.
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 longer developed
Merged with ESLint https://medium.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2
Con Only detects code style violations
JSCS is useful only for enforcing coding styles. As such it cannot detect potential bugs or issues in your code.
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.