[1] https://images.apple.com/media/us/osx/2012/docs/OSX_for_UNIX...
* Open source UNIX foundation
** Support for multiple CPU and GPU cores via Grand Central Dispatch and OpenCL
* Comprehensive UNIX user environment
** Standards-based graphics built on PDF (Quartz), OpenGL, and H.264 (QuickTime)
Your 2011/2012 document gives less assurance towards any future POSIX compliance.This is really there for Swift/Obj-C developers who want to use sockets but have something easier to grok than BSD sockets or NSStream, especially when you need to deal with TLS (Secure Transport, as simplified as it is, is still more difficult to use than saying "open this socket with TLS please"). BSD sockets are also ugly as sin to use in Swift because of rampant use of pointers (it's C, after all) - so there's that too.
What this means is that while BSD sockets will continue to work for the foreseeable future, native cocoa apps and cross platform apps with specialized ports will have a leg up in performance, stability, and safety over dumb ports using BSD sockets.
In other words, you’re free to keep using BSD sockets at your own detriment.
We'll see in 4 years.