Why would I want to scan a qr code on my phone to read shit on a tiny screen you could’ve just printed on the computers display?
Because getting it off your crashed computer’s display and into text format, so it can be grepped or posted in a bug report, is a cumbersome task. (OCR tools are not ubiquitous, convenient, or reliable.) And an impossible task when half the crash dump scrolled off the screen.
Also this is gonna play out great in secured environments where cameras are a no no.
It’s optional.
Leave shit like this to the fuckers with no taste at Microsoft. Kernel panics are supposed to be verbose.
That’s how I felt when the BSoD screen was introduced, but with this new way of using it to reliably deliver more information than ever before, it’s starting to look useful.
As kernel error messages can be quite lengthy especially if including a stack trace and at times not even fitting the contents within the screen, patches posted today allow for condensing kernel error messages into QR codes.
This seems like a regression. We use logs to tell us what’s wrong for a reason.
Why would I want to scan a qr code on my phone to read shit on a tiny screen you could’ve just printed on the computers display?
Also this is gonna play out great in secured environments where cameras are a no no.
Leave shit like this to the fuckers with no taste at Microsoft. Kernel panics are supposed to be verbose.
Because getting it off your crashed computer’s display and into text format, so it can be grepped or posted in a bug report, is a cumbersome task. (OCR tools are not ubiquitous, convenient, or reliable.) And an impossible task when half the crash dump scrolled off the screen.
It’s optional.
That’s how I felt when the BSoD screen was introduced, but with this new way of using it to reliably deliver more information than ever before, it’s starting to look useful.
From the article: