So Dragonfly BSD is the WinNT* of UNIX world, interesting!
"One big part of the goal set will be the creation of a
middle 'emulation' layer which is managed by the kernel
but runs in userland, which will take over all primary
system call entry points (in userland) and convert them
to syscall messages that the kernel understands. 4.x,
5.x, SysV, Linux, and other compatibility sets will be
moved out of the kernel and into this middle layer."
And look where it got NT. POSIX gone. OS/2 gone. NTVDM gone (on 64-bit).
Ultimately we are left with an abstraction layer which abstracts nothing because Win32 is the base level abstraction for all the other abstractions now. Metro, WP etc run on top of it all like a massive house of cards throwing 0x80004005 around to piss off devs. If you know the difference between Nt and Zw you'll get what I mean :)
It's all a big shame because the NT native API and NTFS are absolutely flipping marvelous.
Compatibility layers got destroyed by virtualization as well.
Whole emulation layer thing was a bad idea for NT and this as well.
 Totally undocumented other than the leaked Windows NT/2000 source code a few years ago.
I remember Matt Dillon's DICE C compiler for the Amiga. It was only a trial version so only stdlib stuff. I wrote a little HTML viewer in it which used ANSI codes to display bold text, italic, underline etc.
I was wondering where I had heard the name "Matt Dillion" before. Years ago I was a big Amiga user and a budding programer. I tried the DICE compiler a couple of times but never built anything much, mostly because it was the trial version too.
I wonder what type of computing world we would be in if OSS were more prominent back in the late 80's / early 90's. Imagine what we could have built with an open source compiler (GCC) and a bunch of example code (Github) for the Amiga. Wow! :)
"Good Thing" is often capitalized, or as above italicized, for emphasis in hacker circles. The idea is that it's established jargon  suggesting more specific meaning than a casual goodness remark (whether that's true or not, I'll let you decide). The TM is another such intensifier, with the informal meaning of "distinctive or characteristic", rather than literally trade-marked.
Main negatives about BSDs: more fiddly, not necessarily as well performing as a stable well optimised Linux release (read RHEL/CentOS), some compatibility problems (usually due to crappy programming by Linux-heads), you might have to compile a load of stuff yourself.
The big wins are however: rock solid, wonderful documentation, entirely cohesive base system, small, big enterprise features (ZFS, mandatory access control, tracing frameworks, awesome network stack, security, ACL support and better hardware support.
When I say better hardware support, I mean the drivers all work rather better than their Linux counterparts rather than being plentiful and the supported platforms are plentiful and reliable.
I can drag a 17 year old SPARC64 machine out of the cupboard and just use it.
Both DragonFlyBSD and FreeBSD have improved their scalability on SMP systems over the past year or so. FreeBSD's improvements started in 9.1 and continued in 10; DragonFlyBSD claims to have eliminated nearly all lock contention within the kernel as of it's recent 3.6 release, and initial results look very promising.
Something to consider, which I should point out because your new, is that without BSD you wouldn't have OSX. There's a little BSD in everything (even windows). Another worthy article you should definitely read which explains that BSD is the The single Greatest Piece of Software Ever, with the broadest impact on the world, was BSD
I don't quite understand your question. ygra asserted that the Windows network stack was taken from BSD. This was never true and was kind of a pernicious rumor for a long time. I just assume Greg Lehey's word on it is enough for most people.
There were a few little odds and ends that popped up with BSD license notifications over the years, like the ftp client IIRC. As you say, little utilities that don't amount to much. What is YOUR point?
To all intents and purposes, FreeBSD is dead. If not yet dead, FreeBSD is a carcass whipped out by Apple and friends to say they "support" open-source.
OS X and others have leeched off BSD and made billions, yet every December, this year being the same, FreeBSD has to whip out the begging bowl to raise funding.
Yes, some large corporations employ some of the FreeBSD folk, but what would happen if they stopped employing them? Would FreeBSD be able to build a strong community of developers to accelerate development? I doubt it.
Linux is in a much healthier place and I attribute much of that to licensing as well as technical excellence. The GPL has helped foster an active community around Linux, one that does not allow corporate vultures to simply scavenge off the best bits and usurp direction of the project.
OS X uses portions of FreeBSD including the userland so if you're used to that you probably won't find too many gotchas when using FreeBSD in that regard. I've never touched a straight *BSD install to know the practical differences in configuration and maintenance vs OS X and Linux.
I occasionally get caught by a difference between the BSD and GNU userlands so I've often contemplated giving one of the BSDs a go rather than my typical OS X/Debian/Ubuntu Dev/prod web server preference.
if you look through their drivers, they use a sort of c++ without exceptions, but last i remember from debugging network drivers on osx, they looked like they were forked from freebsd a fairly long time ago, but were for a long time close enough to be able to see the roots(i don't know if it's still like that)
Sorry, I should have mentioned I meant HAMMER under DragonFly, in the sense I can either run a virtualized storage VM or use it on a standalone server. Yes, I don't think there is a working port for Linux.