Clearly a Rust effect.
What would be better is if the scripting was in Python, and a Boa Constrictor compressed the living daylights out of a random shopper.
The Register's Bork column is coming to an end, and to mark the occasion we present the 12 Bork's of Christmas. Today: an unwanted appearance by the Windows command line. No PowerShell for this administrator, oh no. Whoever is behind this screen (spotted by Register reader Sam Owens) has fired up cmd.exe, probably via a script …
that's a touch screen large display (see where it says "touch to explore"?) - looking at the photo it's obvious that somebody was using it when the CMD window popped up and the "click" action of the touch was intercepted by the command prompt.
... and since clicking in a cmd prompt usually PAUSES everything indefinitely because it switches to TEXT SELECT mode... thus it got stuck in text selection mode - notice the "Select" keyword in the title bar and the white rectangular selection cursor in the command prompt window - that's where the window intercepted the touch click action of the user.
(To get out of text selection mode you usually have to press either ESC or enter. Clicking on X in the corner to close the window and terminate the script would also work)
Why did Microsoft call their sleep command "timeout"? I guess they were avoiding collision with Powershell's "sleep" command maybe?
OTOH, I didn't even know there was a "timeout" command, so I've learned something today. That's much easier than my usual hack of using "choice /t 3". (If I can remember it's called "timeout" and not sleep or wait or something else).
Like that odd rumble in the guts that Mother Nature uses to signal "Get your arse to the WC before I fill your socks with shite."
The poor slob then took off at a dead run to make it there before a trip home for fresh knickers was required.
I blame the fruitcake...
Biting the hand that feeds IT © 1998–2022