I tgink I heard of that. Didn't the "scientist" just like self isolate, angry that they didn't fight eachother, while the other passengers became lifelong friends and had a great time?
That was what I was trying to communicate with my comment. It's very difficult to provide the compile objects in rust, and dynamic linking deprives you of many of the benefits of using rust.
It introduces friction if you don't want to open source your code. This friction will drive away many users. I want people to use my code, even in commercial products, so providing libraries in Apache or MIT just makes more sense for that goal. If you have another goal lgpl might be more inline.
Rust libraries are linked statically and aren't replaced easily after compilation, this makes lgpl libraries very hard to use in proprietary code. I don't think what the best action is in this case... I should probably start using lgpl.
I like permissive licenses for libraries, that way you leave room for corporate collaborators, however, all my binaries and end user apps are copy left.
I don't really watch LTT, but I think they we're pretty bad when explaining why they didn't make more fuzz about Honey stealing commissions when LTT found out.
Beautiful :3