(But not the Sun. It ran on commodity 16-bit IBM PCs.)
((I refuse to resist puns. They just flow through me.))
Then you'll like this one.
When I was in college, we had a computer lab full of Sun workstations running Solaris. It was officially called the Solarium.
There's some interesting stuff in there. This one always seemed like a weird problem:
Global variables in Win32 dynamic-link libraries (DLLs) are visible across
processes, so it is important that developers are careful that these globals
do not conflict with any variables within the Unix shared libraries.
At least in the way it is presented. What does variables in DLLs being visible across processes on Windows have to do with variables in other libraries? Of course they need to be uniquely referenced.[0] http://tech.slashdot.org/story/98/11/17/1624254/microsoft-pr...
[1] http://www.linux.cz/pipermail/linux/1999-September/051669.ht...
I personally think that makes for a decent 'moral standing'.
Basically GPL only a problem if you want to create proprietary software, which in turn is typically very much a 'being told what you can do with said software' type of situation, with no code and often incorporating DRM mechanisms to prevent copying.
Edit: For those of you downmodding me for saying that the GPL is a cancerous license, please understand that this isn't a negative connotation - it's simply an aspect of the requirements of the license. It's very likely a good thing, and part of the reason that Linux is doing well while BSDs have languished.
I used to like GPL, so nobody would "steal" my code adding it to a closed source product. I don't care anymore, just use BSD or other credit-where-credit-is-due license: my code was included in a high profile closed source product? Lots of bragging points and free publicity!
You're mistaken if you believe that.
Linux is by far more popular for developers, tinkerers, and cool software projects but BSD is still massive in the server and embedded devices space.
https://en.wikipedia.org/wiki/Usage_share_of_operating_syste...
BSD is a minority in servers, which also reflect my own experience talking with other sysadmins in conferences. Debian and Redhat are huge in the server market, outside of windows shops. Some older system might have novel or a BSD system running together with massive amount of legacy perl scripts, but those companies also complain that they have a hard time finding new employees that can support the old systems.
I understand when people wants to keep making FOSS better by releasing entire projects with a GPL license, but I don't understand when people release simple stuff such as a code example with a GPL license...
This is not a bad thing. It sometimes sucks, but overall it's helped preserve the ecosystem and it has been integral, IMHO, in making sure companies stay honest with their upstream OSS meal tickets.
Which is why cancer is not a good metaphor.
I don't think such language is nice. It is damaging to civil conversation and can only alienate people more. No one likes hearing that what they create is like toxic waste.
Note that it is not the code that these people produce that is toxic, it is what they demand in return (via the terms of the license) that is. The language may not be nice, but it is descriptive of the situation the GPL puts many people into. The GPL essentially seeks to impose the ideology adopted by a subset of folks onto the rest of the world. "We believe code should be free, so if you want to use our stuff, your code must be free too, regardless of what you believe or what your business needs are or what is practical." That is not a very nice stance to have, and so many people do not say nice things about it.
Think of it like someone saying, "Here, I'll do you a favor, but you must change your religion". Having different ideologies is perfectly fine, but enforcing them on others is not.
When MS took over Hotmail they got rid of FreeBSD that was running it.
But MS have used Unix for years. They released MS IE for Unix. (The only person I know who ever used it was on HN.) Perhaps more bizarre was the Windows Media Player for Unix. Their TCP/IP stack was from BSD for ages (and possibly other stuff. The EULA used to refer to the regents of Berkley.)
http://betanews.com/2001/06/18/microsoft-we-use-freebsd/
https://news.ycombinator.com/item?id=5182249