3 ms·
http://ycombinator.com/newsguidelines.html http://ycombinator.com/newsguidelines.html > In Comments >Be civil. Don't say things you wouldn't say in a face to
by danford 13y ago
http://ycombinator.com/newsguidelines.html http://ycombinator.com/newsguidelines.html
> In Comments
>Be civil. Don't say things you wouldn't say in a face to face conversation.
>When disagreeing, please reply to the argument instead of calling names. E.g. "That is an idiotic thing to say; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3."
Public facing code shouldn't be closed source. Sure, if you want to run something on your own and for your self, you don't have to share that with anyone, but when you put something out into the wild that can't be conclusively shown to not be malicious it should be treated like malware.
Edit: and also, what do you think the government should do for the people when it comes to digital rights? Or do you believe corporations know what's best? I for one don't believe in either.
- happyscrappy 13y agoI am sorry if that offended you but I take issue with the idea that adding more restrictions improves freedom. If you want to download possible malware that is your choice.
- lutusp 13y ago> I take issue with the idea that adding more restrictions improves freedom. Yes, but that isn't an idea the OP posted, it's an idea that you posted. A discussion of software license types doesn't automatically lead to either a preference for one kind of license over another, or the idea of governmental involvement. Those were things you made up on your own. > If you want to download possible malware that is your choice. Both closed and open-source code are susceptible to malware. The issues of licensing and malware are orthogonal. Closed-source code should in principle prevent malware, but it's quite obvious that it doesn't. Open-source, by being visible and readable, should reveal any vulnerabilities and prevent malware, but that doesn't work either, primarily because the more interesting vulnerabilities aren't obvious to someone reading the code. Which means your argument is just an argument.
- happyscrappy 13y agoHe was arguing that closed source software should be disallowed. Who else but the government is going to make such rules? Yes I brought freedom into it. I agree that both open and closed will have malware, so what is the point of banning closed software if not "freedom"?
- lutusp 13y ago> He was arguing that closed source software should be disallowed. He did not make this argument. He argued that closed source has serious drawbacks -- he never suggested that it should be "disallowed". Find the word or an equivalent word -- but you must find it in his posts, not yours. If I complain about women, am I saying they should be disallowed? Only to someone who invents positions for other people, then proceeds to object to the positions he has invented. > Who else but the government is going to make such rules? Is Apple under government mandate to have a closed-source system? Is Red Hat under government mandate to have an open-source system? Neither is true. The government is not involved at all, in any way, period. > Yes I brought freedom into it. Yes, you did, after inventing arguments no one made, using claims about society that aren't part of reality. > ... so what is the point of banning closed software if not "freedom"? You fabricated this entire argument out of whole cloth. No one advocated "banning closed software", no one brought up government, no one brought up freedom. These are all parts of your private fantasy.
- danford 13y agoI'm scared by the idea that I could one day have a neural implant with closed source code running on some insecure network all because the people of this time were too dumb to realize how software could affect them. Perhaps we should have laws that guarantee some form of open-ness but allow closed source code to exist on some sort of semi-to-fully-anonymous fully-encrypted secondary communications network?
- lutusp 13y ago> I'm scared by the idea that I could one day have a neural implant with closed source code running on some insecure network all because the people of this time were too dumb to realize how software could affect them. It's a reasonable concern. People have already been injured and killed by software errors, both open and closed, so this is definitely on the table as a reasonable issue. > Perhaps we should have laws that guarantee some form of open-ness but allow closed source code to exist on some sort of semi-to-fully-anonymous fully-encrypted secondary communications network? My view is that we should let people sort this out without government involvement. Right now there are open-source companies and closed-source companies, and people get to vote with their feet. If closed-source causes problems or is more expensive or whatever, people can choose the alternative. Same with open-source. There are any number of cases where government involvement turned out to be counterproductive, and I think this might be one of them. Remember that government can't just bust in and start issuing orders, they have to be invited by the voters. And sometimes, if things go wrong, they get voted out again. Freedom of speech -- clearly a government issue. Open-source versus closed-source software -- sorry, how this is a government issue doesn't immediately occur to me.