News for hackers. Stuff that matters.
Re:License to Use JSLint for Evil by MaxBarraclough on Thursday April 14, 2022 @04:36PM (#31032937)
Right. It's probably the second worse place to put jokes, next to an employment contract.
Re:License to Use JSLint for Evil by zarzavat on Thursday April 14, 2022 @11:09PM (#31036283)
Not really. Nobody actually pays attention to open source software licences whatever you write in them. They're just window dressing. Who isn't violating the attribution requirements of 1000-odd npm dependencies?
Re:License to Use JSLint for Evil by MaxBarraclough on Friday April 15, 2022 @04:26PM (#31045395)
> Nobody actually pays attention to open source software licences whatever you write in them. They're just window dressing.

Plainly untrue. Various companies (including Google and Apple) have strong opinions on the GPL licences, especially the GPLv3.

Many of us see it as a red flag when a seemingly Free and Open Source project turns out to use a licence approved by neither the FSF nor the OSI.

> Who isn't violating the attribution requirements of 1000-odd npm dependencies?

You may be right that much web frontend development is a sloppy free-for-all with no regard for compliance and no contact with the legal department, but not all software is developed on this basis.

Re:License to Use JSLint for Evil by skissane on Friday April 15, 2022 @12:59AM (#31036723)
That’s why attribution requirements are stupid. Of course, as a matter of politeness and ethics, one ought to acknowledge the work of others you build upon. But elevating it from an informal principle to a formal legal requirement puts people in the unpleasant position of having either to deal with endless and ever-changing attribution bureaucracy, or just ignore it all and hope nobody ever complains (or sues). Zero attribution licenses don’t do that to people.