When comparing JSLint vs Terminal.app, the Slant community recommends JSLint for most people. In the question“What are the best plugins for Sublime Text?” JSLint is ranked 18th while Terminal.app is ranked 28th. 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.
Ranked in these QuestionsQuestion 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 Default terminal on Mac
Since it is already installed by default, you don't need to worry about finding and installing another terminal.
Pro Light on System Resources
Terminal.app lighter uses less system resources than iTerm having the same number of windows, tabs and processes going on.
Pro Great compatibility
Works with everything.
Pro Easily open man pages
By right clicking on a highlighted string you can easily search through the man pages for that string and the man page will open in a nice pop up window.
Pro Excellent xterm emulation support
Pro Beautiful
Terminal has nice colors and font options.
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 Updates are released rarely
Terminal usually gets an update when any new MacOS version is released, which is every couple of years.
Con Tab names are volatile
The tab names never stick -- it's imperative that this should work.
Con Background images are stretched rather than clipped
Con Occasionally crashes
Working remotely with a full buffer may cause complete terminal app crash.
Con Home and End keys require shift being pressed
