9 ms·
The guy must be damn sure about how cool his projects are, because there's a situation where your project is cool enough for company to use but they won't becau
by minoru 14y ago
The guy must be damn sure about how cool his projects are, because there's a situation where your project is cool enough for company to use but they won't because of GPL. It would probably work with startups (they're flexible and in a hurry — they'll take the coolest thing around without a second thought), but it may not work with bigger companies. Quite contrary, I believe that big companies tend to use software licensed under BSD, though I have no personal experience with that.
I also want to express my gratitude for a different view of startups — I definitely never thought of them as a bunch of guys who would take as much open source software as possible but hide the fact, all in a name of perceived smartness, innovativeness and productivity.
- zck 14y ago>...there's a situation where your project is cool enough for company to use but they won't because of GPL. He obviously realizes that. From the article: >I would actually rather nobody use my software than be in a situation where everyone is using my gear and nobody is admitting it.
- minoru 14y agoYes, he does. I wrote my comment to emphasize the other side of the coin, not to fill some gap that wasn't covered in the article. It must be kind of mistake here (I've read the posting guidelines but I'm still a newbie, thus more prone to errors), so I propose to finish the discussion.
- nemik 14y agoDid you miss the part about dual-licensing, GPL and paying for non-GPL? It worked out quite well for MySQL IIRC.
- minoru 14y agoDual-licensing works for MySQL but it may not work that well for smaller projects that are easier for company to re-implement from scratch. There's a possibility that GPL may be too high price for company to pay, and it's a price, too; you as a developer pay it when you choose GPL over BSD. The purpose of my previous comment was to point that out.
- chc 14y agoI don't understand what you're suggesting the downside here is. They might decide not to take my code, lock it up in a proprietary system and profit from it without me getting anything out of it? How am I harmed by them not doing all that?
- minoru 14y agoIf your code was used by some company you may use that fact on the interview or to promote your project further, but if you are using GPL you are risking the chance to do so.
- chc 14y agoThis is a piece of software that they aren't willing to pay for (remember, you're offering it under a proprietary license as well) — how likely do you think it is to help you if they silently use your code and don't tell anyone? You can't even "use it on the interview"†, because they just took it silently and didn't tell you they're using it. † Incidentally, I hope never to interview with this hypothetical company that isn't willing to pay for value-providing software but would find the fact that I gave it away for free highly compelling.