byteorder

Burntsushi has written many important crates in the Rust ecosystem. He started with licensing under Unlicense exclusively, until people requested a dual license with MIT. See this issue from 2016 for more details - https://github.com/BurntSushi/byteorder/issues/26 Almost all of the Rust ecosystem is dual licensed under MIT/Apache 2.0, so this combination is a bit unusual. But the presence of MIT means that it hasn’t been a problem in practice.

Ditto, I guess? :P (But obviously with the position on the Unlicense flipped.) To address your indictment head-on: you suggesting the 0BSD as a better alternative is really missing my point. The 0BSD is not an alternative for my use case. The Unlicense is one of the very few overt "political" acts that I inject into the software I produce. Its purpose is to make a statement. The 0BSD doesn't do that IMO, so it's not actually an alternative that meets my advocacy goal. You and Rick Moen seem to have the same apparent blind spot for this. See my conversation with him that started here (which might also clarify some aspects of my own position): https://github.com/docopt/docopt.rs/issues/1#issuecomment-42... And finally, note that my dual licensing scheme is exactly a response to the "problems pointed out by quite a few people": https://githu

You might care to notice that the resignation was announced by Andrew Gallant—more commonly known as BurntSushi[1]—who is one of the most well-respected, talented, and prolific contributors in the wider Rust community. Amongst other things, they are the author of ripgrep[2], the regex[3] crate, and the byteorder[4] crate. They have multiple projects which are amongst the most-downloaded crates[5] in the Rust ecosystem. One would struggle to find more than a handful of people who have done more "actual work" for Rust than Andrew. [1]: https://blog.burntsushi.net/about [2]: https://github.com/BurntSushi/ripgrep [3]: https://github.com/rust-lang/regex [4]: https://github.com/BurntSushi/byteorder [5]: https://crates.io/crates?sort=recent-downloads

Hmmm, maybe there is some confusion here. At least for ripgrep in particular, it has always been dual licensed under the MIT and the UNLICENSE[1]. This was itself a continuation of a decision I made a bit earlier with regards to another project[2]. Namely, I had been using only the UNLICENSE. But dual licensing with the MIT allowed folks with a more conservative risk profile to use the project. But the point of linking to VS Code's decision was to say that I have direct experience with situations in which a copyleft license might have inhibited use of my software. That is, it's an example that runs counter to my goal of as many people using my code as possible. This doesn't mean copyleft is never used in popular projects or that copyleft somehow perfectly inhibits popularity. I mean, obviously that's not true. But the existence of popular