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
Far from bug proof. You can write as many logic bugs as you want (as that's what happened here), but it'll save you from a common class of potentially devastating memory safety and data race bugs in safe Rust.
11 Comments
onlinepersona@programming.dev · 21 pts · 32d
Providing fodder for the "ermagerd, rust is evil" crowd, even though it has nothing to do with rust.
somegeek@programming.dev · 15 pts · 31d
No it's just a news about the pointless, corporate rust rewrite of GNU coreutils being a shitshow.
lengau@midwest.social · 3 pts · 30d
Oh then it must be because of the MIT license!
/s
Papierkorb@feddit.org · 9 pts · 30d
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.
eutampieri@feddit.it · 2 pts · 30d
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
onlinepersona@programming.dev · 1 pts · 30d
The term "cuck license" for MIT and similar licenses is a good one IMO.
ZombieCyborgFromOuterSpace@piefed.ca · 1 pts · 30d
I agree with you on that one.
Skullgrid@lemmy.world · -7 pts · 31d
but I thought rust was bug proof and completely safe?
TwilightKiddy@programming.dev · 13 pts · 31d
Safe? Eh, may be. Bug proof? You need a bug proof brain first.
fif-t@fedia.io · 6 pts · 31d
Far from bug proof. You can write as many logic bugs as you want (as that's what happened here), but it'll save you from a common class of potentially devastating memory safety and data race bugs in safe Rust.
ZombieCyborgFromOuterSpace@piefed.ca · 1 pts · 30d
It's as bug proof and safe as the developers using the language.