In this talk, Jamund Ferguson discusses the history and philosophy behind ESLint, and walks through the benefits of using ESLint in a number of different situations when linting to maintain code quality.
The History of Code Linting
JSLint was created in 2002 by Douglas Crawford, and has since been viewed negatively by many due to the tool’s strict ruleset. In 2011, the more flexible JSHint was created as a backlash against JSLint, yet the tool still faced many limitations.
Have you ever tried to modify JSLint and add a new rule? One does not simply modify JSLint. There are thousands of lines of code where the parser is mixed with the rule engine, therefore, when you need to change a rule, the rule may be in three or four places in those thousands of lines.
About Jamund Ferguson
Jamund is a UI Engineer for PayPal. In his current position, Jamund helped launch the new beta PayPal consumer website using node.js, Backbone, HTML and CSS with a focus on improved performance and mobile usability. He has also contributed to the open source Kraken node.js server project.
Find more of Jamund’s work and talks at http://www.jamund.com