by bichiliad on 11/30/17, 1:06 AM
I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases.
Remember that:
- They learned about this yesterday
- They had as much heads up as the general public did
- They are a large company.
I don't disagree that the apparent QA quality from Apple software isn't what it used to be, but we all have to take these sorts of things with a grain of salt. I've certainly been in situations like this before.
by mberning on 11/30/17, 4:35 AM
From a quality standpoint Apple is a shadow of its former self. For me a large number of the more recent features in macOS and iOS don’t work reliably. Things like handoff, text message forwarding, enabling tethering from the Mac, etc. are 50/50. These kind of things used to be Apples bread and butter. Taking ideas like these and making them “just work”. And now the security regression are creeping in. I would love to see them get back to very simple product lines and a more minimalist approach to software features.
by excalibur on 11/30/17, 12:23 AM
Quick show of hands, who here is surprised that this patch broke something?
by k_sze on 11/30/17, 6:50 AM
The article says “
if file sharing doesn’t work”, but is it ok to just run this command line fix anyway?
I’m not sure if file sharing is broken for me. I don’t use it right now. But I’m afraid I might run into this bug in the future when I eventually use file sharing, and then I will have forgotten about this fix, and end up spending hours scratching my head and head-desking.
by cmlndz on 11/30/17, 1:00 AM
I think this shows the poor state of Apple’s QA. Theorically there should be a list of predefined tests with a binary output, to pass the test or not. Before deploying anything, tests must be run and passed.
It seems the procedure is very human-dependant.
by LCDninja on 11/30/17, 6:21 AM
Seriously!
I can’t even install 10.13.1 on my Mac Pro 2013 - computer acts like its bricked until rebooted a number of times (and when it finally boots we’re back at 10.13).
This also means I can’t install the latest security update that fixes the root problem (and yes, i’ve changed the root password to mitigate).
OSX is becoming more like Windows every day.
by pwinnski on 11/30/17, 12:39 AM
This is why it should take more than 24 hours to put out a patch for an operating system.
by yuhong on 11/30/17, 12:53 AM
I remember the emergency Java patch after Flashback. I think it also had an issue.
by nkkollaw on 11/30/17, 12:42 AM
What a mess.
by nixpulvis on 11/30/17, 1:14 AM
I guess now we get to see where all the holes in apples fucking automated tests are... meanwhile I'm happily running Arch ;)