✨ Nora Tindall  🪐

Honest question: what do you expect when using GPL in your code? I personally use MIT.

When someone uses my code in another software project that they then distribute, the code for that project is also available. MIT does not require this, so I don't usually use it.

The problem of GPL is that it also requires derivative work to be under GPL as far as I know, that's why I don't use it and use MIT instead, because GPL basically makes commercial usage impossible.

That's not at all true. It just means the resulting product has to be open source. You use the commons, you contribute back to the commons.

"Unless you are talking about chocolate cake, most cake is vanilla." I think that a company that uses my work should contribute their changes back. If they don't want to, they can go chew rocks.

What a fallacious comparison. Most commercial code is closed source and that's it. It is the reason why companies like Apple, Microsoft or Google actively avoid using GPL and have removed a lot of GPL dependencies. When it comes to code, you could even say that GPL harms OSSW.

If you want to restrict the usage of your code to whatever you want, it's your choice. But I am not sure still so as to what is the point. Any company would prefer to code their own library rather than have to open source the whole piece of software.