Hacker News Reader

Comment by throwaway132448 | Hacker News Reader

Thanks, you are much more accepting of these failure modes than me, that is for sure!

For a clock on an always-powered device to be unable to keep track of time just speaks of embarrassingly bad design to me. The available state to reconcile is just not that complex, even with networked time thrown in. Not to mention it is a protected feature that most other applications cannot manipulate anyway.

Sophos & Tableau probably fall in the crap software bucket too, but thankfully I'm not obliged to use them.

My default mode is to vote with my wallet, but with OSes our choices are sadly more limited, less avoidable, and have a much greater impact when they break basic features, so I want to hold them a higher standard. The whole reason I run Mac & not Linux is to save time with something turn-key, but when it's still an unstable platform moving beneath you it might be time to contemplate the full-time switch!

View on HN

Compared to the Windows registry, Apple’s usage of plist files for system state, are a bastion of stability.

That said, they are still files and weird stuff can happen. It shouldn’t, but it can.

It is entirely possible a third party app is responsible for this, just as much as it’s possible it’s a bug in the OS.

If you read any of the links you supplied, you’ll see how easy it is to delete the file. This being the case, it’s not beyond the realm of possibility that something else damaged the file.

Sophos had no reason to quarantine the critical file it did that Tableau used. I’ll happily bitch about Tableau till the cows come home, but this was absolutely not one of them.

Again - we were prepared to 100% blame Tableau. We had no idea that the issue was a missing file and we’d have never ever discovered it unless the Security Manager had pinged me.

So, it’s very easy to blame the broken thing from being broken. But sometimes it’s not the broken things fault.

No one should be expected to cover every last single potential issue that can affect something - it’s a fools errand. You do the best you can and move on.

If the issue here is, from what it sounds like, a corruption plist then the solution is to apparently delete it and let the OS heal itself after.

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!

Reply on news.ycombinator.com