4 ms·
Excellent summary. The language of economics is often very good for succinctly communicating things like this. As far as what should be done, that's a lot tri
by davidw 13y ago
Excellent summary. The language of economics is often very good for succinctly communicating things like this.
As far as what should be done, that's a lot trickier. My inclination is that it should mostly be limited to universities and government having something of a bias for open source with very liberal licenses. That's a big vague, but I'm a bit tired, so it'll have to do. I do not think the government should get involved in funding software it doesn't actually need in a big way.
- gwern 13y agoI'm not sure either. The academia model seems very ill-suited for FLOSS because, while it does incentivize releasing source so other people can use it, it doesn't incent any sort of ongoing maintenance or improvement except in the rare case where doing so can generate more papers and publications (which, unless the initial functionality was amazing, means that the released source will quickly become useless and bitrotten - saw it happen multiple times in Haskell-land). One mode which does seem to work very well is Google's Summer of Code. For pretty modest investments, it seems to yield a lot of useful functionality, and because it piggybacks on existing projects & communities, the improvements seem to generally stick. I've watched the Haskell-related Summer of Codes for years now (http://www.gwern.net/Haskell%20Summer%20of%20Code http://www.gwern.net/Haskell%20Summer%20of%20Code) and there's been some great stuff accomplished via them.