Ask HN: Why you do open source?
21–30 of 84 posts
Re: Ask HN: Why you do open source?
#22Re: Ask HN: Why you do open source?
#23Re: Ask HN: Why you do open source?
#24Re: Ask HN: Why you do open source?
#25I get paid to do it ;) All the code we write at the company I work for is Free Software (though not all is available online).
So you don't really open source, the company you work for does.
I've also released some code of which I'm the copyright holder as Free Software, mainly plugins for other applications. I've licensed it as such because I thought others could benefit from it.
Re: Ask HN: Why you do open source?
#26Re: Ask HN: Why you do open source?
#27Re: Ask HN: Why you do open source?
#28I don't get to do that much for my usual contract work (yes, I'm one of those developers - sorry).
Re: Ask HN: Why you do open source?
#29- Avoiding being alienated from my own work.
- To produce software which anyone can use, regardless of financial or geographical situation.
- To produce better quality software by not reinventing the wheel and by the ability to modify or reuse existing code.
Re: Ask HN: Why you do open source?
#30I use because:
- I feel much more confident supporting something which I know I can dig into and observe the function of. This can give me and understand of what I'm doing wrong, allow me to work around it or possibly patch it entirely. Contrast this with the helplessness of troubleshooting the black box of closed software.
- It's cost effective. Money not spent on expensive licenses and implied support contracts can be applied elsewhere. Since much of my work deals with public funds, I feel particularly obligated to maximize value.
- I feel what I learn using OSS is more transferable, and applicable to other systems and problems than closed software.
I contribute because:
- I think sharing discovery and tools and building on the work of others is key to our success as a species. It feels completely natural.
- It opens the door for symbiotic improvements. Personally, I seem to be pretty good at find a novel perspective on a problem, but have little knowledge of how to code it efficiently. Sharing my code with someone who knows how to do those things benefits us both.
- To learn by practice and example.