Skip to content
HHackerTube.videoSurprise me

Using JSLint For Evil

Using JSLint For Evil on HackerTube: recommended by 2 Hacker News commenters across 2 separate months, 2013–2023.

ryantravistate

talk · evergreen

Open on YouTube

A three-minute clip in which Douglas Crockford explains why he allowed the JSLint reference implementation to be used for evil. It recounts the license clause and how corporate lawyers reacted.

Why Hacker News recommends it

Linked in licensing threads as a short, funny story about the 'no evil' clause and IBM's request for an exception.

people recommended it
2
separate months
2
strong recommendations
0
discussed on HN
2013–2023
“This reminds me of Douglas Crockford's classic story about the JSLint license”
— tlrobinson, Jul 2020, in “Does saying “Fuck You AWS” constitute offensive content?”

What HN commenters said

6 Hacker News comments link this video. Each one links back to its thread.

SonOfLilitJul 2017Recommends

David Crockford puts a "don't use this for evil" clause in the license for all software he releases, creating some interesting situations: ▶ this video (2:44 and worth it)

in “Ask HN: Software licensing excluding military use?” · View on HN

computerOct 2013Recommends

See this 3 minute presentation fragment about the "Do not use JSLint for Evil" license clause: ▶ this video

in “How to Corrupt an SQLite Database File” · View on HN

eastonApr 2021Cites it

That's what I was talking about. Crawford said in a talk he had to make an amended licenses for corporations (namely, IBM), who had lawyers that needed to be able to get around the evil restriction. ▶ this video

in “SQLite Plus: Missing SQLite functions” · View on HN

tlrobinsonJul 2020Cites it

This reminds me of Douglas Crockford's classic story about the JSLint license containing a "The software shall be used for Good, not Evil" clause: ▶ this video

in “Does saying “Fuck You AWS” constitute offensive content?” · View on HN

rogerbinnsMay 2013Cites it

That doesn't work at all if it is the actual wording. For point 1 you can find warranty wording in any number of open source or creative commons licenses. For the second, objectionable requires a definition. For example many would consider the US drone assassination program objectionable, and hence tar US companies and people with the same brush. Does that mean US companies and people can use the software? How many steps do they have to be removed (eg is providing the payroll software to the defense contractor a problem?) [link] ▶ this video Because of copyright laws, people can do virtually nothing with software. If you actually want to give the user freedoms - see [link] - then pick a well known free software license since it will have already addressed all these issues.

in “Show HN: What do you think of this short End User Licensing Agreement?” · View on HN

btillyNov 2023Critical

When you know that history, IBM asking for an exemption to the JSLint license becomes less funny. Watch ▶ this video (2 minutes) to hear the story from the developer's point of view. Then consider how many totalitarian states today are using IBM computers to track their population. The developer might not realize it, but IBM lawyers absolutely know that they can be fairly accused of using JSLint for evil.

in “In the bad old days we had Punchcards. How did people deal with that?” · View on HN

Topics & tags