Ask HN: Commercial licenses for Rust embedded software libraries?
It's also the kind of library that, once it's written, sometimes the chunks of code that were tricky to figure out tend to get copyright-violatingly copied&pasted between projects (and, today, laundered through Copilot-like software), and soon treated as public domain.
With the idea in mind that maybe one or a few companies might want to use this library, saving them engineer-weeks of development, combined with the idea that I love receiving money...
What do you think about, instead of the LGPL license I'd normally use, making it GPL, with an added statement to contact me about other commercial license options?
And any other comments on when different kinds of embedded systems product developers are willing to pay for libraries, and what kind of pricing and licensing terms are appropriate?