I wrote a small app to display a bitrate graph of video files, and posted the code on GitHub with the GPL2 license. A few weeks later someone uploaded it to the Mac App Store and sold it for 7$, the only difference was the name.
Ask HN: Have you ever regretted open-sourcing something?
31–40 of 454 posts
Re: Ask HN: Have you ever regretted open-sourcing something?
#32https://blog.getpaint.net/2009/11/06/a-new-license-for-paint...
Re: Ask HN: Have you ever regretted open-sourcing something?
#33Re: Ask HN: Have you ever regretted open-sourcing something?
#34I wrote a small app to display a bitrate graph of video files, and posted the code on GitHub with the GPL2 license. A few weeks later someone uploaded it to the Mac App Store and sold it for 7$, the only difference was the name.
If they're not complying with your license terms, sue them. If they are then I guess you missed the boat on money.
Re: Ask HN: Have you ever regretted open-sourcing something?
#35Steve Ballmer nailed it when he said GPL is a cancer. No professional programmer wants to open source anything, but once one competitor does it, he must follow suit to stay competitive.
Re: Ask HN: Have you ever regretted open-sourcing something?
#36Steve Ballmer nailed it when he said GPL is a cancer. No professional programmer wants to open source anything, but once one competitor does it, he must follow suit to stay competitive.
Re: Ask HN: Have you ever regretted open-sourcing something?
#37Re: Ask HN: Have you ever regretted open-sourcing something?
#38This was one of those niche industry specific things that no one would give a crap about if it was open sourced other than the competitor in the market.
Principal architect was tossed on the street for that one.
Re: Ask HN: Have you ever regretted open-sourcing something?
#39Got death threats because I wasn't prioritizing stuff people were requesting, said nah I'm done
I had death threats once for raising a github issue!
Re: Ask HN: Have you ever regretted open-sourcing something?
#40I tried to open source a weekend personal project while at $BIGCO via their "Invention Assignment Review Committee". It turned into a minor bureaucratic nightmare and I was ultimately never given the OK to release it, or any clarity over whether my employer was choosing to assert an IP ownership interest in it. In retrospect, I wish I had never notified them of its existence, and released it under a pseudonym instead…
Whenever I join a company I always create a bunch of made up names on my “prior inventions” list. When I open source something I just name it after something I put on my list if the description is close enough.
Great suggestion to make in advance placeholders to contain side projects.