3 ms·

> If you're not charging or patenting the code, why not open source? Code might be working perfectly but if it is ugly as heck you might not want to show it of

> If you're not charging or patenting the code, why not open source? Code might be working perfectly but if it is ugly as heck you might not want to show it off (for personal reasons, or not). You might be using code from other, paid applications (example: faviconographer.com). Maintenance(?), if you open source it people might want to e.g. create lots of issues or such. Mental tax but might only apply to larger popular projects. Startup costs, maybe related to the code quality. I don't like throwing code out there. I like to make some form of documentation, clean the code, add some examples and neat readme.md's and so on. And this takes time and effort.

52-6F-62 9y ago
Yeah, not bad points. Especially licensing questions. I was asking, after all: why. Personally, though, I'd be happy if I could convince people to take time to view my half-finished code and offer suggestions, support, or improvement. I run too many half-baked public repos as is because I usually get carted off to, or distracted by, other projects. I guess the maintenance thing depends on your personality, and the state of your project. If it's under development, you don't have to worry about everybody so much. If you're trying to run a release, sure. Even then you can ignore everybody and just tell them you'll do as much and that it's only there for auditing. But if you're trying to convince people to download your native, unreviewed application? My questions were very directed, and not general, so my intention wasn't to sound so sweeping as that.