|Original author(s)||Douglas Crockford|
2018-02-05 / February 5, 2018
|Type||Static code analysis|
According to the Free Software Foundation, this clause makes the license non-free. The clause has also prevented JSLint-related software from being hosted on Google Code and from being included in the Debian free software package repositories. Because of this restriction, according to Crockford, IBM asked Crockford in 2011 for a license to do evil, such that their customers could use it.
In 2011, Anton Kovalyov created a fork, called JSHint. The main motivation behind the creation of JSHint was to provide a "less opinionated" and "more configurable" way for developers to analyse code.
In 2013, Nicholas C. Zakas created ESLint. Both JSLint and JSHint were lacking the ability to create additional rules for code quality and coding style. After contributing to JSHint, Zakas decided to create a new linting tool, ESLint, where all rules are configurable, and additional rules can be defined or loaded at run-time.
Copyright 2002 Douglas Crockford. All Rights Reserved Wrrrldwide and Beyond!
I give permission for IBM, its customers, partners, and minions, to use JSLint for evil.
[JSLint] has gotten uncomfortably opinionated
[..] JSLint was getting a bit too opinionated [..]
designed to be less opinionated and more configurable
JSLint complaint: not configurable enough. JSHint complaint: still not configurable enough [..]
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your Digital Marketing and Technology knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.Visit defaultLogic's partner sites below: