4 ms·
Ask HN: What are the drawbacks of releasing my language under GPLv3+link exc?
Hello,
I was going to publish the source of my language under GPLv3 with the linking exception.
To me it looks like an ideal option: it protects the project and its contributors, and it doesn't result in any inconveniences for companies, since a compiler is not a library that has to be linked. And of course it can be used to develop proprietary software.
But several people are confident [1] that if I don't go for a copyfree license like MIT or Apache 2, lots of developers and companies will be scared off from contributing.
I'd understand if it were a library, then most simply wouldn't be able to link it. But you don't link a compiler, and the linking exception allows to use the stdlib without any limitations.
If they want to modify the compiler, it's easier for companies to contribute rather than support their own fork any way.
And if someone really needs a copyfree license, I could always have a separate license for them.
What are the drawbacks I'm not seeing?
Thanks
[1]: https://github.com/vlang-io/V/issues/22
- NonEUCitizen 8y agoNobody will use it -- you need to reduce, not add friction to people trying out your language. Nobody wants to read the license, or negotiate a special license for a new language.
- amedvednikov 8y agoBut why, what's the friction?
- oaw-bct-ar-bamf 8y agoSpending time to read the license + exceptions More importantly: Trying to convince upper management that this license will be ok to use.
- amedvednikov 8y agoAgreed, GPL is complicated. I'm now considering MPL. It allow static linking without complicated technical requirements.
- amedvednikov 8y agoI'm now considering MPL 2.0. Seems to be easier.
- CalChris 8y agoBSD is easier still.
- amedvednikov 8y agoYeah I decided to go for MIT in the end :)
- rurban 8y agoGPLv3 is one the most used SW licenses on github. https://github.com/search?utf8=%E2%9C%93&q=license%3Agpl-3.0&type=Repositories&ref=advsearch&l=&l= https://github.com/search?utf8=%E2%9C%93&q=license%3Agpl-3.0... => 934,174 gpl-2: 377,640 mit: 3,719,721 mpl-2.0: 37,146 I believe it's by far the best license, even if evil companies like apple, microsoft, facebook or google will not touch it with a 10foot pole. They would need to open source their services using it then.
- SamReidHughes 8y agoIt’s the AGPLv3 they really won’t touch. Companies still use gcc.
- rurban 8y agoGPL3 took the service part from Affero, that's why the GPL3 is also strictly forbidden there.
- SamReidHughes 8y agoNo, that's the AGPLv3.