The Changelog: Software Development, Open Source

You can FINALLY use JSHint for evil (Interview)

Dec 20, 2020
Guest
Mike Pennisi
In this discussion with Mike Pennisi, the maintainer of JSHint, we dive into the complexities of software licensing and how they can hinder open-source projects. Mike shares the journey of JSHint, particularly the significant shift from a restrictive license to a more accessible MIT license, enabling broader adoption. He discusses the ethical implications of licensing choices and the emotional weight of such decisions. The conversation also highlights the importance of maintaining human connections in the developer community, stressing empathy and authentic engagement.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
ANECDOTE

JSHint's Origin

  • JSHint forked JSLint to offer configurability in linting rules.
  • This allowed developers more control over code style preferences.
ANECDOTE

JSHint's Clever Naming

  • The name JSHint cleverly capitalized on JSLint’s reputation for strictness.
  • This clearly communicated its value proposition of a more flexible linter.
ANECDOTE

Mike Pennisi's Involvement

  • Mike Pennisi's first open-source contribution was to JSHint.
  • He later became a maintainer, focusing on ES6 support alongside Rick Waldron.
Get the Snipd Podcast app to discover more snips from this episode
Get the app