FWIW I license any libraries I create under MIT for the reasons you cite in your article. Basically, anything that is designed for reuse gets licensed for reuse. However, I have started to appreciate the GPL for applications that I create. I like knowing that derivatives of those will stay open.
My name is Matteo and I'm a cloud solution architect and tech enthusiast. In my spare time, I work on open source software as much as I can. I simply enjoy writing software that is actually useful.
That's a perfectly reasonable use of the GPL and I definitely agree with you. Thought you might as well consider the MPL 2.0 (the one used for example by Firefox) which still protect your code without influencing other's application that might link to yours, for example through some API of some kind
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
FWIW I license any libraries I create under MIT for the reasons you cite in your article. Basically, anything that is designed for reuse gets licensed for reuse. However, I have started to appreciate the GPL for applications that I create. I like knowing that derivatives of those will stay open.
That's a perfectly reasonable use of the GPL and I definitely agree with you. Thought you might as well consider the MPL 2.0 (the one used for example by Firefox) which still protect your code without influencing other's application that might link to yours, for example through some API of some kind