News for hackers. Stuff that matters.
Re:WWDC 2017 and What It Means for Developers by aparadja on Saturday June 17, 2017 @07:03AM (#14575302)
It was also almost offhandedly announced (in session 707) that they are deprecating network kernel extensions, with no real replacement API in sight.

That's an existential crisis for 3rd party firewalls.

Re:WWDC 2017 and What It Means for Developers by orf on Saturday June 17, 2017 @11:10AM (#14576211)
Does this mean little snitch may stop working?
Re:WWDC 2017 and What It Means for Developers by aparadja on Saturday June 17, 2017 @12:47PM (#14576592)
That's certainly what it looks like. They told developers to "talk to us" if the change is a problem. I opened a support ticket immediately, but haven't yet heard back. I'm sure the people at ObDev have done the same.
Re:WWDC 2017 and What It Means for Developers by Khaine on Sunday June 18, 2017 @09:14AM (#14580502)
Things like murus[1] will still work although it leverages the first party firewall (pf)

[1] http://www.murusfirewall.com

Re:WWDC 2017 and What It Means for Developers by microcolonel on Saturday June 17, 2017 @11:06AM (#14576185)
macOS is a wasteland, if anyone is investing in it today then they are a fool or have been fooled.

The IPC performance is still abysmal (noticeable latency in several applications) after 16 years of kernel development. The scheduler is meh, the features offered by the kernel are generally meh. The UI and multimedia libraries were quite good, but they neutered them by incrementally removing customization opportunities, and now there's little left. No way to install a codec or container in Core Audio or Core Video, so you can't play or Quick Look Opus or VP9 or a Matroška file in standard applications. Their OpenGL drivers are garbage, absolute putrid garbage, especially on the integrated graphics; they still only support OpenGL 4.2 (read: the year 2011) on any GPU, and on Intel's GPUs performance is often 60% worse than performance on Linux and Windows (which are generally on par). If their Metal implementation shares its shader compiler with their Intel OpenGL implementation, then it's likely that you will never see any performance benefit from Metal on Intel graphics because your application is probably shader bound due to their drivers. And if we're being fully honest, if they were trying to make developer lives easier, they would add Vulkan support, but they refuse.

Re:WWDC 2017 and What It Means for Developers by skybrian on Saturday June 17, 2017 @12:49PM (#14576608)
Wow, as a user I don't care all that much about any of that.

I expect many users will feel the same, so developers will keep making apps for them.

Re:WWDC 2017 and What It Means for Developers by pjmlp on Tuesday June 20, 2017 @08:54AM (#14594202)
For the developers at WWDC 2017 none of those items are relevant.