A company like Apple should have complex enough tools to perfectly capture system state at the time of the bug so that they can reproduce it

▲

eminence32 5 hours ago | parent | next [-]

I don't work at Apple, so I can't comment on that. But that doesn't always help. There's been plenty of times where I have a full HAR file from the user and I can clearly see that something went wrong, but that doesn't always mean I can reproduce the issue. (I recognize a HAR file doesn't represent the complete state of the world, but it's often one of the best things a backend developer can get)

	▲	fragmede 5 hours ago \| parent [-]
		Reminds me of this Raymond Chen Microsoft blog post: https://devblogs.microsoft.com/oldnewthing/20241108-00/?p=11...

▲

wat10000 5 hours ago | parent | prev [-]

That’s easy enough. The hard part is doing so without capturing a bunch of email, messages, and other private data that happens to be in memory at the time.

▲

Barbing 5 hours ago | parent [-]

Ignorant question, if privacy didn’t matter and they had an atomically identical machine, would there still be plenty of edge cases where it was the printer or the Wi-Fi causing the issue?

In any case I would have said it sounds difficult on every front

	▲	wat10000 4 hours ago \| parent [-]
		I should be more precise. Capturing the system state isn’t too hard. Turning that into a reproducer may be quite hard, because of things like you say. There are certainly a lot of bugs that such a capture would make easier to figure out, but it wouldn’t be a panacea.