Also, I agree with the reference code for most standards being licensed under a permissive license. It makes a standard like VP8 or Vorbis or ODF have less problems competing with entrenched opponents which are not freely available, such as OOXML, MPEG, etc.
TCP/IP is a good candidate.
What I wonder is why there are no complaints when Microsoft and Apple make BSD code proprietary, but only when the GPL makes sure there is an implementation that stays freely available which is something permissive licenses don't do very well.
The other problem with BSD licenses is there's no patent grant, so Apple could take BSD code, fork it for themselves, and then sue other people who use that code or even the developers of the code themselves. The Apache license, MPL, CDDL, or even the MS-RL are good alternatives to BSD. Apache is BSD-like but makes sure that people can't take it and sue the author or give their own code to it and sue people for using that. The CDDL, MPL, and MS-RL go a step further and make sure that the software stays under the license which is otherwise very BSD like with the addition of an Apache style patent grant. Perhaps the BSD license isn't fit for the times it finds itself in and other licenses would be safer for developers and their eventual end users.
As for the BtrFS FUD, BtrFS is designed to be better than ZFS, it's just a lot newer. The fsck tool cannot repair the file system yet, but there are many fewer cases where the file system is likely to become corrupt than in competing file systems anyway. It would be more of a disaster to release a fsck tool which is not finished and could end up damaging the file system itself than making people wait for a few more months. If it makes people who would otherwise complain about problems in BtrFS which would eventually be fixed anyway, so much the better. These types of problems create FUD that never dies, long after the code is fixed. File systems are not "sexy" they are tools. As a tool, their job is to enable you to do yours with minimal interruptions and demands on the user. ZFS uses a lot of CPU and RAM, in fact, they even tell you not to use it without at least a GB of RAM. it scales up, but not down. Which Sun admitted themselves. It's not a good general purpose file system and I would hate to find myself stuck with it on a tablet or netbook or a computer that is more than a few years old. BtrFS has resolved these problems.
As to the GPL 3? If the BSD people hate it because it protects the user from companies that sue over the code they made or using DRM, then I don't give a rats ass what the BSD people think of it. If they are siding with companies who use DRM, then to hell with them from my perspective.
What can I say about Clang? It likes to spit out code that is broken, slow,or doesn't do anything at all. It's the part of the LLVM project that rides the short bus. Ironically, the best thing I've seen LLVM doing only works on Linux. Gallium3D can optimize GL shaders with it. Since nothing on any BSD uses Gallium3D, you can forget bragging about it there.
Servers? I don't run a server, I run a desktop. Linux is great as a desktop, BSD can only barely be used as one, and even then you need a perfect match to the limited hardware pool it supports. Linux is not unpopular on servers. Some of the biggest and most profitable open source companies got there with Linux. But I don't need to tell you what Red Hat is or where their stock has been heading for the last few years, do I?