Live data from Hacker News

Ask HN: Startup shutting down, should we open source?

news.ycombinator.com

31–40 of 40 posts

Re: Ask HN: Startup shutting down, should we open source?

#31

I wouldn't do it. It'd be like a dead lover. Don't get suckered into prettying up her corpse on the off chance your opinion of necrophilia changes.

100%.

Dealing with 5 year old code is okay now. In 10 years it will cause you pain. It's like going back to an ex after you lose attraction. It never works out and hurts both parties (in this case your users, because you won't maintain it or want to pretty soon)

Re: Ask HN: Startup shutting down, should we open source?

#32
post #9

Earlier quoted context omitted.

What's to exploit? The company won't exist anymore...

People's servers hosting it. I will not be officially responsible but anyway not nice. I may be just paranoid

This is the risk we accept when we use something like this. I think it's fine to put it up. If there are security issues, the community of people that use it can respond accordingly.

Re: Ask HN: Startup shutting down, should we open source?

#33

[random advice from the internet] If you really want to put an open source project out in the world the right way, taking what you learned and building an appropriate code base might be a better route. And if you don’t really want to put an open source project out in the world, that’s okay. Your customers had an interest in paying you enough to stay in business. They did not pay enough (and maybe because you did not…

What does "appropriate code base mean"? If I did it, then I would of course cleanse a bit here and there, make the corpse prettier as somebody wrote in another comment. More thant that, however, is an amount of work which is just not viable. Thanks!

I think he means properly maintained and worked on.

Re: Ask HN: Startup shutting down, should we open source?

#34

I wouldn't do it. It'd be like a dead lover. Don't get suckered into prettying up her corpse on the off chance your opinion of necrophilia changes.

100%. Dealing with 5 year old code is okay now. In 10 years it will cause you pain. It's like going back to an ex after you lose attraction. It never works out and hurts both parties (in this case your users, because you won't maintain it or want to pretty soon)

And or if you got any dependencies (even to "open" 'stuff') when vulnerabilities and bugs arise that will break the backwards compatibility to your codebase you will definitely be tempted/lured/asked to spend "only 5 mins" to update it.

Just don't. Keep a copy wherever others suggested, keep a photo in the folder with the ex-bf/gf think about it every few years (I wonder how she is doing - in a Morty voice) and quickly move on!

Re: Ask HN: Startup shutting down, should we open source?

#38

If you don't open source it, it will either wither and be abandoned or someone clever will "open source it" for you in a way you may not like. Software is hard to kill. See Softpress Freeway as an example in the same industry.

Hey, I do not quite understand your statement. How should this happen? Ex Devs? Hacking my git account? Or do you mean something else?

Re: Ask HN: Startup shutting down, should we open source?

#39

If you don't open source it, it will either wither and be abandoned or someone clever will "open source it" for you in a way you may not like. Software is hard to kill. See Softpress Freeway as an example in the same industry.

Hey, I do not quite understand your statement. How should this happen? Ex Devs? Hacking my git account? Or do you mean something else?

Something else: I support some long term clients still using some 1990s software that I've ported to run within a VM on modern hardware. I ended up using developer tools made in the 2000s to decompile the executable and make changes to the software, others have done so and posted their own version. These tools were not available when the developer walked away, so they probably never envisioned these changes.

With AI and other tools developing rapidly, I wouldn't be surprised if someone was able to do things with your code in ways you didn't expect, even if you choose not to open source it yourself.

Post reply on HN