I give permission for IBM, its customers, partners, and minions, to use JSLint for evil.
^ "Re: The Software shall be used for Good, not Evil". ^ "Various Licenses and Comments About Them". ^ a b "JSMin isn't welcome on Google Code". ^ "JSLint source file, including license". All Rights Reserved Wrrrldwide and Beyond! List of tools for static code analysis, JavaScript. In 2019 TSLint was deprecated in favor of ESLint with a TypeScript integration. In 2016, Palantir Technologies created TSLint, which is the TypeScript equivalent for ESLint. In 2016, CodeKit also praised ESLint for "finding more issues", being "far more configurable", and being "the industry standard" for JavaScript syntax checkers. In 2015, a comparison published by SitePoint, recommended ESLint above JSLint, JSHint and JSCS. In 2016, the JSCS Team joined the ESLint project and has since discontinued maintenance of the JSCS tool. ESLint also supports linting the latest versions of JavaScript, aka ECMAScript 2015 and above. 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. Both JSLint and JSHint lacked the ability to create additional rules for code quality and coding style. The main motivation behind the creation of JSHint was to provide a "less opinionated" and "more configurable" way for developers to analyse code. In 2011, Anton Kovalyov created a fork, called JSHint. It has since inspired various other tools. JSLint is considered by some to be the first JavaScript syntax checker. 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. It had also prevented JSLint-related software from being hosted on Google Code and from being included in the Debian free software package repositories. 
The sole modification was the addition of the line " The Software shall be used for Good, not Evil."Īccording to the Free Software Foundation, this previous clause made the original license non-free. Since 2021, JSLint uses the FSF / OSI approved Unlicense license.īefore that, the JSLint license was a derivative of the MIT License. It was created in 2002 by Douglas Crockford. It is provided primarily as a browser-based web application accessible through the domain, but there are also command-line adaptations. I have still have trouble in seeing how "We can compose objects out of sets of parts" using the eventuality function in the chapter.JSLint is a static code analysis tool used in software development for checking if JavaScript source code complies with coding rules. I was reading Ch 5.5 of the book in title.
0 kommentar(er)
