Linked by David Adams on Tue 8th Apr 2008 16:33 UTC
BSD and Darwin derivatives "I am very happy about the direction in which the Mac OS X GUI is going, although sadly many Mac users aren't interested in (or don't know about) the "lower levels" of the Macintosh Operating System. Have you ever wondered why the Terminal greets you with the words "Welcome to Darwin"? Why do BSD and Mac OS share certain bits of code? Why does Wikipedia describe Mac OS X as a graphical operating system? Today we're going to take a look at the underlying open source technology which powers your fancy Leopard OS - the hidden core set of components, named Darwin."
Permalink for comment 308785
To read all comments associated with this story, please click here.
RE[3]: What BSD could have been
by nevali on Tue 8th Apr 2008 23:10 UTC in reply to "RE[2]: What BSD could have been"
nevali
Member since:
2006-10-12

"Could have been??? more users use BSD (Darwin, FBSD, NetBSD, OpenBSD...) on their desktop than any other open source OS.

I've always chuckled at the way many BSD advocates try and portray the disadvantage of the BSD license in producing code and software that is used to provide others like Apple with a free ride to produce totally different and incompatible systems. "Oh well" the BSD people say. "It makes us the most used desktop system around!"

Keep thinking the above if it gives you some pleasure, and some comfort.
"

Surely that depends on what your aims are?

If your aim is to write code and know that millions of people use it because your license is so liberal, and you get satisfaction from knowing that (evidently lots of people do, after all), then who's been disadvantaged?

If your aim is to write code with the intention that nobody can fork it in a way which prevents others from doing the same thing (as per the GPL and similar licenses), then obviously the BSD situation isn't going to be amenable to you.

Neither is inherently right or wrong, it's just that different people value different things.

(As an example: I build websites for clients for a living; I know that thousands of people use my code every day, and to me that's what makes the job worth doing; they don't even know that I'm responsible for it (unless something goes wrong and I have to talk to them!). Other folk don't really get anything from that scenario, and would much rather, say, build a site for themselves, and enjoy the fact that people know who built and runs it).

Reply Parent Score: 6