IT help desks HATE this one simple trick.
pebcak
“The definition of insanity is doing the same thing over and over again and expecting different results” except frustratingly this actually does work when half the time the solution to technical issues is turning on/off, uninstalling/reinstalling, restarting, or reloading the program. So I guess nowadays the definition of insanity is “doing the same thing over and over again for a period longer than 30 minutes before googling to see if anyone else has had the same problem”
New take on an ancient meme (same artist)
It’s more like a remake rather than a “new take”.
Sure, fair, meant more a new take visually
A “retake,” if you will.
A remake, if you will.
Tangential fact!
Some sites use session recorders, which report back to the website owner when users rage click like that.
So there’s a chance if a website has made you rage click, its owner has replayed your visit to the site to try to figure out what went wrong.
it’s too bad a mouse click is not an analog input as to also associate pressure with frequency.
Indeed, as a result session recorders are all missing “sort by: likelihood of mouse damage“
…hmm maybe unless they see rapid left clicks, then nothing, then spammed right clicks… an eventual close via the keyboard…
And done nothing about it.
I must not be visiting those websites.
Bugs following you! 👻
Poor YouTube guy trying to figure out why I liked and unliked that video that I got emotional over 34 times
My coworkers do this when any program takes longer than 1 second. Frequently spam clicking on a button that does something, so they end up with 14 copies of whatever they were trying to print or the program opening 14 times
That one door achievement in The Stanley Parable be like…
There’s also the “You can’t jump.” achievement, kinda similar.
The way this works on Windows is as follows:
The operating system has a subsystem called “messages” to tell applications about things such as mouse clicks. Every time you click on the application, the OS drops a message* in the app’s queue. When the app is ready it reads the messages off the queue and decides what to do.
Windows can’t really tell what your application is doing, but it can see whether or not the app is reading the messages or just letting them pile up. So if no messages are pulled for 5 seconds, Windows throws up the “not responding” screen. The rest of the 316 clicks are just stuffing the message mailbox to the brim.
Linux is mostly very similar, except the UI stuff is not a part of the core OS, and there are several different systems.
- On Windows a mouse click is actually two messages: “button pressed” followed by “button released”.
What a coincidence. That is the exact number of honks to get traffic moving again.
I’ve seen this multiple times and am only now noticing they destroyed their mouse in the last panel
This reminds me of a good lesson my uni IT/video shooting & editing teacher often said: “Your problem is not about what the computer does, it’s what you clicked it to do. Stop. Think for a momenent.”
“Please reconnect mouse to continue.”
This is how you know someone who wins the Whomp Mario Party mini game also has IT rage.
Are you telling me there is a secret number of clicks for each error? Ohhh boy why didn’t I learned this before!
Because it’s secret.
