I do the work because I see it as payback for all the great open source software I use all the time.
I’d like to see an attempt by useful freedom respecting software projects to deploy patents to combat non-free reimplementations.
A GPL license that grants you rights to the backing patent as long as the software you develop with it is also released under the GPL license.
Use the library for closed source software? Copyright violation. Reimplement the software under another license? Patent violation. Create something slightly different and call it the same thing? Trademark violation.
I’d provide links to some discourse of this, but honestly I think it’s better to search “can you patent software in the US” and do a brief read of various sources, because the terminology between them can seem somewhat counterfactual to eachother.
On the other hand, Meta was found torrenting terabytes of books and for them it's a nothingburger. The rules are really meant for commoners.
Something that isn't brought up enough in the "rewrite everything in Rust" discussions is that the API guidelines explicitly recommend MIT/Apache to "maximize compatibility" (i.e., corporate friendliness, or developer and user exploitation): https://rust-lang.github.io/api-guidelines/necessities.html#...
Your project has been around for a while, but it's crazy to me that anyone still open sources anything under MIT (or similar) in the era of LLMs. Are they that confident in their job security? Are they already independently wealthy? Frankly, even a proper copyleft license is likely to just be ignored, or the code laundered through an LLM-assisted rewrite, by these companies. I prefer to just keep anything I can't sell all to myself rather than release it, at this point.