Ask HN: How to give away a popular(ish) codebase?
I developed a project for NodeJS a few years ago that has gotten quite popular since then, and is something that I know a lot of businesses and individuals use. Last I checked it's getting 5k+ downloads/month (that obviously doesn't mean 5k new people per month). It's a binding to a C++ library and I worked out most of the bugs last year.
The thing that sucks? V8 has changed considerable, as has NodeJS's api. I'm getting tickets to keep up, but I just don't have any motive to do the work (I've moved on to golang). I've stopped caring about Node, as I actually think it's not that great of a platform anymore. I think it's useful for small, one-off things, but I'm not really interested in developing with it anymore. Any suggestions for getting rid of this thing in a way that's fair to the people who are relying on it for their organization?
3 comments
[ 3.2 ms ] story [ 18.9 ms ] thread> fair to the people who are relying on it for their organization?
If there are large-ish organisations that need it, they could take it over or pay you for further development if you are interested in doing that.
It's nice of you to think about them, but you don't owe them anything. They didn't pay you for your work. Every developer must understand that if they choose to use a free framework that is being maintained by only 1 developer, they're putting themselves at risk of the framework being discontinued.