Sure, I understand and appreciate what you're saying. I just don't think it's ok. I don't care how simple the fix is. I don't really even care about where to a

Sure, I understand and appreciate what you're saying. I just don't think it's ok. I don't care how simple the fix is. I don't really even care about where to apportion blame - because I want everyone to be better. This isn't asking anyone to "cover every last single potential issue that can affect something". These are all things 100% within Apple's control. The only thing that changed between my clock working and not working, was upgrading the OS. So what I do care about is that it wasn't implemented defensively enough to prevent a system critical component from failing - by people who should know better. A lot of things don't work very well (including me!) when the clock can't be relied upon. I don't know when this all became OK exactly but it feels like we've reached a tipping point of shittiness where even the most basic things cannot be relied upon, and that shittiness then propagates all the way up through the stack, until it's the end-user that has to deal with the many ways in which it manifests. Anyway, appreciate the debate thanks!