That’s my biggest pet peeve with it honestly. My theory is still that it’s a mistake that modern languages/tooling create a LICENSE file for you. In the before-times, when someone posted a project without then you told them and they educated themselves. Some chose GPL, some MIT, all fine, as long you do it with an educated mind. But now, the file gets created, technically legally binding contract of sorts, and the authors simply never bothered to check.
Change my mind: Linux is only still highly relevant because of GPL, not despite of.
Cargo doesn’t create a LICENCE for you, and it doesn’t set the metadata like npm. It even tells you to go choose a license when you try to publish a crate without one
Oh then it must be because of the MIT license!
/s
That’s my biggest pet peeve with it honestly. My theory is still that it’s a mistake that modern languages/tooling create a LICENSE file for you. In the before-times, when someone posted a project without then you told them and they educated themselves. Some chose GPL, some MIT, all fine, as long you do it with an educated mind. But now, the file gets created, technically legally binding contract of sorts, and the authors simply never bothered to check.
Change my mind: Linux is only still highly relevant because of GPL, not despite of.
Cargo doesn’t create a LICENCE for you, and it doesn’t set the metadata like npm. It even tells you to go choose a license when you try to publish a crate without one
I agree with you on that one.
The term “cuck license” for MIT and similar licenses is a good one IMO.