- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
You must log in or register to comment.
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.
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.
i love how this is like a sentence for sentence uptranslation of my comment. thank you for sharing :)
(non industry person, heads up)
We use logs to tell us what’s wrong for a reason.
sometimes u can’t access logs easily, no? especially if something is real busted
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?
phone usually stays on when ur trying to reboot and finick with stuff, whereas computer screen turns off. other alternative to keep a persistent copy i guess would be to print it out but that’s not eco friendly
Also this is gonna play out great in secured environments where cameras are a no no.
can’t speak to this but hopefully u can disable it?
Leave shit like this to the fuckers with no taste at Microsoft. Kernel panics are supposed to be verbose.
that qr code is massive, looks pretty verbose to me. idk i like moves to make linux more accessible. people are always calling for the ‘year of the linux desktop’ and then turn around and do backlash to try to keep things obfuscated and unfriendly to the average human, especially, again, where u can probably disable it if wanted. idk i guess im pretty critical of that tendency.
people are always calling for the ‘year of the linux desktop’ and then turn around and do backlash to try to keep things obfuscated and unfriendly to the average human
To be fair to both of these groups in my impression those are usually separate people. People definitely have different visions for what good design is here.
The thing that strikes me as bad is when Unix conservatives (for lack of a better term) actively resists features to support use in modern, bit-mapped graphics as opposed to 70’s teletype terminals etc. But that’s just a terrible position, not necessarily hypocrisy, assuming they don’t care about Linux as the kernel in a desktop operating system for people whose hobby is not configuring their computer.
this does explain quite a bit, thanks for the clarification
, where u can probably disable it if wanted.
these things should be opt-in, not opt-out. Opt-out is the way Microsoftism get (and have already gotten into) Linux.
looks like its opt in good news
From the article:
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.
What in the Microsoft Windows is going on here?
Potterdung’s hand in it probably. That said, it makes it much easier to extract information about an error condition on a machine you might not have keyboard access to… assuming you do have screen access to, tho.
