4 ms·
A lot of people probably don't open source their web code because it could open them up to attacks, but it also probably wouldn't be that interesting. It never
by hacknat 13y ago
A lot of people probably don't open source their web code because it could open them up to attacks, but it also probably wouldn't be that interesting.
It never would have occurred to me to open up my work's rendering pipeline, it's just to boring and ho-hum for words.
- rwallace 13y agoInteresting versus boring isn't really the criterion, though. I mean, doubtless there are some programmers who read code for entertainment, but they're in a minority. Usually what we care about is what the code does. Right now I'm using the excellent Dragon NaturallySpeaking, which is useful enough to me that I bit the bullet and paid for a license. But it would be even more useful if it were open source, not because I want to read the code for intellectual stimulation, but because there are several bugs that would be easy to fix, would make it even considerably better, that the developers refuse to fix (a common enough occurrence) and nobody else can fix (a problem peculiar to proprietary software).
- IgorPartola 13y agoExactly. And even if they only open sourced the UI portion of it, I bet it would be a net benefit.
- npsimons 13y agoIt never would have occurred to me to open up my work's rendering pipeline, it's just to boring and ho-hum for words. You say that, but if there's anything I've learned from HN, it's that nothing is "too boring". I'm not advocating that you do open up your rendering pipeline, but you never know who might find it interesting, useful, or even help you make it better.