5 ms·

So will BSD sockets follow OpenGL's path to deprecation?

snuxoll 8y ago
Doubtful, there's no reason to throw it out since Mach is still UNIX-y. 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.
- weiming 8y ago
  For domain sockets specifically, there is this Swift library which does various heavy lifting with the C APIs: https://github.com/IBM-Swift/BlueSocket https://github.com/IBM-Swift/BlueSocket
- kitsunesoba 8y ago
  Network.framework isn’t just easier to use, it performs better and is generally safer 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.
pieterr 8y ago
As long as Apple wants to keep macOS POSIX-compliant, the sockets remain. [1] https://images.apple.com/media/us/osx/2012/docs/OSX_for_UNIX_Users_TB_July2011.pdf https://images.apple.com/media/us/osx/2012/docs/OSX_for_UNIX...
- kevin_b_er 8y ago
  From your link: * 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.
- saagarjha 8y ago
  Unrelated, but there's a whole lot of information about someone named Ernest Prabhakar there…
doctorsher 8y ago
There are many big name apps on the app store that are intended to be as cross-platform as possible (reducing platform specific code), and as backwards compatible as possible (4 latest releases of iOS). For these reasons, they are built on top of sockets. I supremely doubt Apple will tell these companies to pound sand; they are much more important to them than those affected by the OpenGL / OpenCL deprecation.
- Yoric 8y ago
  Not today. We'll see in 4 years.

Doubtful, there's no reason to throw it out since Mach is still UNIX-y. 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.

weiming 8y ago
For domain sockets specifically, there is this Swift library which does various heavy lifting with the C APIs: https://github.com/IBM-Swift/BlueSocket https://github.com/IBM-Swift/BlueSocket
kitsunesoba 8y ago
Network.framework isn’t just easier to use, it performs better and is generally safer 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.

pieterr 8y ago

As long as Apple wants to keep macOS POSIX-compliant, the sockets remain. [1] https://images.apple.com/media/us/osx/2012/docs/OSX_for_UNIX_Users_TB_July2011.pdf https://images.apple.com/media/us/osx/2012/docs/OSX_for_UNIX...

kevin_b_er 8y ago
From your link: * 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.
saagarjha 8y ago
Unrelated, but there's a whole lot of information about someone named Ernest Prabhakar there…

doctorsher 8y ago

There are many big name apps on the app store that are intended to be as cross-platform as possible (reducing platform specific code), and as backwards compatible as possible (4 latest releases of iOS). For these reasons, they are built on top of sockets. I supremely doubt Apple will tell these companies to pound sand; they are much more important to them than those affected by the OpenGL / OpenCL deprecation.

Yoric 8y ago
Not today. We'll see in 4 years.