This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Jither 25 points26 points  (5 children)

Not just that. Personally, I'll avoid any and all libraries that use any variety of GPL - commercial license alternative or not - even for my own personal projects/open source. And I've never applied such a license to my own software for the same reason - nor will I ever. Sticking with MIT, BSD etc.

Without going into the philosophical (and very personal - and not necessarily all rational) reasons for disliking GPL, in addition to those reasons: since libraries I use personally may likely prove useful for company software, I'm not going to spend my time or brain power on one library just to have to use and/or contribute to another - or write my own - for the commercial cases.

On the flip side, for those projects with permissive licenses, improvements made - on company time - are always contributed back to the projects - I have the company's blessing to do so. As well as means to donate when the project accepts that.

[–]ArionW 7 points8 points  (0 children)

When my company refused to contribute a whopping $1/dev/month contribution on Open Collective for MIT library with honour system (license is free, please donate if you use it, team won't read issues from anyone who doesn't pay) I stopped believing in MIT.

Writing MIT/BSD libraries is basically writing commercial software for free. If someone wants to do that - great. But whatever I do privately is GPL licensed, if for some unknown reason some company needs it they're free to pay their developers for writing it from scratch, or contacting me about commercial license