Free up to 1MM monthly messages. No credit card required.
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.
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.
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
Take a look at the top trends that are the most effective in attracting customers and reducing churn, and how you can incorporate...
Comparing the major game engines: Unity vs Unreal Engine vs Corona SDK vs GameMaker Studio, including the benefits and cons of...
Sockets (aka socket programming) enable programs to send and receive data, bi-directionally, at any given moment. This tutorial...