QR silliness
-
From CP newsletter Linux is getting its own Blue Screen of Death - The Verge[^]
"full-screen message that displays a QR code to get more information on what’s causing the boot issue."
Because everyone knows that the open source community is known for its completeness and dedication to creating excellent documentation.
-
From CP newsletter Linux is getting its own Blue Screen of Death - The Verge[^]
"full-screen message that displays a QR code to get more information on what’s causing the boot issue."
Because everyone knows that the open source community is known for its completeness and dedication to creating excellent documentation.
If you can print a QR code, you can print a text message. I can't think of anything that would need more than a few lines of 80 character text. Which should also get written to one of the log files - unless its the disk that's gone kaput. I don't get it. You want me to find my phone, scan a QR code, hopefully have cell reception, and then squint at a web page that tells me something that could have been written to the console? Madness. IMHO, systemd is a solution looking for a problem. Maybe Sys-V init scripts didn't quite measure up to today's requirements, but having simple scripts which anyone with a little shell knowledge could understand was preferable to the complex beast that systemd has become. Like EMACS, its in danger of becoming its own OS. Maybe next they'll add a scripting language based on lua, just to "improve" things ... </rant> Dang. I said that last bit out loud. We're doomed, I tell you! DOOMED! (and not in the id software way....)
"A little song, a little dance, a little seltzer down your pants" Chuckles the clown
-
From CP newsletter Linux is getting its own Blue Screen of Death - The Verge[^]
"full-screen message that displays a QR code to get more information on what’s causing the boot issue."
Because everyone knows that the open source community is known for its completeness and dedication to creating excellent documentation.
-
From CP newsletter Linux is getting its own Blue Screen of Death - The Verge[^]
"full-screen message that displays a QR code to get more information on what’s causing the boot issue."
Because everyone knows that the open source community is known for its completeness and dedication to creating excellent documentation.
But of course ... :-D
-
If you can print a QR code, you can print a text message. I can't think of anything that would need more than a few lines of 80 character text. Which should also get written to one of the log files - unless its the disk that's gone kaput. I don't get it. You want me to find my phone, scan a QR code, hopefully have cell reception, and then squint at a web page that tells me something that could have been written to the console? Madness. IMHO, systemd is a solution looking for a problem. Maybe Sys-V init scripts didn't quite measure up to today's requirements, but having simple scripts which anyone with a little shell knowledge could understand was preferable to the complex beast that systemd has become. Like EMACS, its in danger of becoming its own OS. Maybe next they'll add a scripting language based on lua, just to "improve" things ... </rant> Dang. I said that last bit out loud. We're doomed, I tell you! DOOMED! (and not in the id software way....)
"A little song, a little dance, a little seltzer down your pants" Chuckles the clown
agreed. Over the years I've developed the general disposition of "get off my lawn." The family wanted iPhones. Sigh, okay. 4+ years later, Apple did something, backups stopped working, etc. The problem is, I cannot login to any of my customer sites without 2 factor authentication. Now we get QR codes for crashes? I really don't want to have to use my damn phone for development work.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
From CP newsletter Linux is getting its own Blue Screen of Death - The Verge[^]
"full-screen message that displays a QR code to get more information on what’s causing the boot issue."
Because everyone knows that the open source community is known for its completeness and dedication to creating excellent documentation.
-
I know that a lot of people think so. I never understood why. A few months ago, there were lots of people claiming that the days of UPC codes (the bar codes used to identify all sorts of merchandise, read at the cash register) was counted. Why? Well, it the way into the future. Why would that be? It is future proof! So what makes it future proof? Oh, you silly old fool - any smartphone can read UPC codes, don't you see? Smartphones can't read UPC codes! That is right. A smartphone with a QR reader app but without an app to read UPC codes can read QR but not UPC. I guess there are UPC reader apps as well, to give you a smartphone that can read UPC, but maybe not QR codes (if the QR app was never installed or taken out in a spring cleaning). Usually, it isn't needed: Most UPC codes have the numerics in readable format below the bars. QR codes don't. When the reader can't read the bars, because the tag has been crimpled, torn or washed out by water, the operator may read the UPC digits and type in on a keypad (that happens regularly at my grocery store with tags wrapped around vegetables). With QR codes, you would be lost. What would be the cost of replacing UPC codes with QR? You would have to replace or update every single cash register in the Western world. You have to re-label the books in most libraries (the ISBN, International Standard Book Number, is a subset of UPC) and all the bar code readers of the library. The printers making UPC labels would have to go. The electronic price tags on the shelves that is used nowadays do not have room for a QR code to replace the UPC displayed nowadays, at least those used in Norwegian stores. And so on. It would be tremendously expensive. It might be worth it if it had some significant benefits to it, but so far, the only benefit I can see - for applications where UPC does a perfectly satisfying job - is that smartphone QR readers are far more common than smartphone UPC readers. I cannot see that justifying the expenses.