Hacker News new | ask | show | jobs
by master-lincoln 959 days ago
But the dev here claimed they created this tool for themselves. If that is the case, why not let everyone else use it for free too if you maintain it for yourself anyway.

I wouldn't answer questions or read feedback then as a dev because it's not a product really, but why not go that route?

2 comments

This is very privileged. Opening an app up for public use is exponentially more effort and the developer deserves to be compensated for it
How is it exponentially more effort if you don't care about what the public has to say about the app? Where is the privilege in my argument?
It's the difference between having an internal library at work and having an open source library in github. If you are using it for yourself, backwards compatibility, and breaking things are not necessarily issues
> If you are using it for yourself, backwards compatibility, and breaking things are not necessarily issues

It's also not an issue if you publish it. External users might complain, but that is their problem if you make it clear this is a personal project