It has nothing to do with Rust. Permissive licenses are more popular with new projects. Rust is more popular with new projects.
The stats show that people are more likely to be attacked by a shark on days when they had ice cream. Eating ice cream does not make you more likely to be attacked by a shark. They are just both things that happen at the beach.
So many Rust projects are dual-licensed under Apache or MIT. It’s just a convention that many Rust projects have adopted. Yes, it’s true that there’s nothing intrinsic about Rust the language that requires a certain license type. But it doesn’t mean that the Rust community hasn’t adopted a convention of licensing with pushover licenses. That’s my point.
It has nothing to do with Rust. Permissive licenses are more popular with new projects. Rust is more popular with new projects.
The stats show that people are more likely to be attacked by a shark on days when they had ice cream. Eating ice cream does not make you more likely to be attacked by a shark. They are just both things that happen at the beach.
So many Rust projects are dual-licensed under Apache or MIT. It’s just a convention that many Rust projects have adopted. Yes, it’s true that there’s nothing intrinsic about Rust the language that requires a certain license type. But it doesn’t mean that the Rust community hasn’t adopted a convention of licensing with pushover licenses. That’s my point.
Hmm, interesting trend. I didn’t know about this.