Meh, probably mostly "you can't modify this, you can't steal it, you can't claim it as your own, you can't use it to hack people, ect..."
You can't steal any software, because software can't be owned. Also, people can't be hacked; what you are probably referring to is cracking, often misrepresented in mainstream media as "hacking".
Not a problem for me. And since I'm the user, that's all that matters to me.
Of course, you have the right to use non-free software if you choose. I would just rather you didn't claim it to be free when doing so.
Isn't that what Beta Testing is for? Peer review? And bug reports? And customer service?
Just because you don't have an army of programmers examining your code doesn't mean it's not being evaluated.
The key word we're looking at here is "peer". Proprietary software testers and developers are not peers, because they don't have equal rights to the software. A more appropriate term would be "minion testing", which has a fundamentally different outcome because the testers can't see the whole picture, only what the developers want them to see.
Also, scientists are often funded by people who can see a profit in the application of science. (ie. technology). Profit results in more funding.
While I agree with this, I also fail to see what relevance it has to the conversation.
If all software was open source, it would be like Linux:
Lots of Variations(not the kernal but you know what I mean) that crash very very easily.
You forgot to finish that sentence: "... as well as lots of variations that can run for years without a glitch." In any case, this isn't true, because typically what happens is that a program only gets forked when someone is really unhappy with the current direction it's taking, and then there will be a giant flame war and everyone will end up switching to one of the forks and the other one dies. It's very rare that you get a successful split with enough users to maintain both projects independently. GNU+Linux distributions work slightly differently because they're not programs per se, but collections of programs designed to work together (with varying degrees of success at this aim).