Earlier quoted context omitted.
I drew exactly the opposite conclusion. Go with BSD if you want Apple to steal your code and contribute back nothing to the community (how much have they given back to Free/NetBSD?).
This keeps being brought up, the whole apple not contributing back to FreeBSD, but I would urge you to please look through FreeBSD's CVS history to find all of the places that Apple HAS indeed contributed back (I've made several comments with links to such sources on HN before). Apple also has an entire website dedicated to the various pieces of source code for their OS, and other tools, and are actively developing c…
a) out of date or unrealized (for which they are entitled to do with BSD code, but when it comes to GPL I file complaints)
b) redacted and uncompilable (they purposely remove source code for specific targets that is still listed in the build environment, or hold back critical header files for dependent libraries)
c) limited in scope (they release WebCore, because it is LGPL, but they actually /don't/ release a lot of WebKit)
Also, it is quite clear to everyone involved that the reason that they are actively developing Clang/LLVM is so that they can avoid gcc 4.3+, when it went GPLv3. It was hard enough for them before: gcc was the one place they have been unable to redact and hoard their ARM contributions, but with GPLv3 the situation becomes untenable for them.
So, since then, Apple's Xcode compiler has rapidly slipped out of date, and now they are forced to take over development of a BSD project just to stay competitive.
Frankly, this is actually a /win/ for the GPL: despite Apple's claims, Clang/LLVM is still very very far behind GCC in terms of correctness and compliance (certainly with recent specifications, like C++0x), which has made Apple's less-free choices result in an increasingly "dispreferred" deployment target for many projects.