What? The explanation makes no sense. Where did the user reconfiguring his CPU to overheat upon pressing control come from?188.8.131.52 06:27, 11 February 2013 (UTC) Edit: I was referring to the actual explanation which has since been edited, not the comic itself. I understood that, but the explanation was quoting stuff that wasn't in the comic.184.108.40.206 18:35, 12 February 2013 (UTC)
- It's not 'from' anything. It's just an extreme and humorously far-fetched example of how a user might put a bug to use. He used the bug so he wouldn't have to reach for his actual control button, a 'horrifying' hack which works for him. 220.127.116.11 17:21, 12 February 2013 (UTC)
No idea where this coming from, but reminds me this bug and this reaction to it. Firefox is good example in general: about:config was obviously CREATED to make much more settings available that is sane to put in configuration windows. On the other hand, this problem is old, so the comix is probably about some other, more recent problem, possibly in completely different software. -- Hkmaly (talk) 09:39, 11 February 2013 (UTC)
I'm constantly running stuff like [email protected], but I usually underclock my components to conserve power and lengthen the lifespan. However, I created a macro that overclocks my GPU at the press of a button, and I use it to act as a heater for my room whenever I get cold. It works. Those children could follow my example. 18.104.22.168 15:05, 11 February 2013 (UTC)
I think this is a jab at Windows 8, only an upside-down one - since the comic is about a lone protester as opposed to the general dissatisfaction with Tile World. Also: Let's wire the computer components (and a heat sink) into an office chair. Would sell like crazy in the North.
I think it would be nice to include in the explanation, for people unfamiliar with Emacs, that most macros require you to type Control something. It's common to remap Ctrl to the Caps Lock position so that it's easier and faster to reach. 22.214.171.124 17:32, 15 February 2013 (UTC)
I've learned long ago to never assume that my personal expectations will help everybody. To never ignore feedback from your core users (who else would stick around and use such a buggy system?). And that if you taking other's choice away to save them from themselves, try to give a quick alternative, such as a hint on how to modify the script to look for prolonged space-bar commands and engage control button (perhaps that user is disabled?) - E-inspired (talk) 23:53, 27 February 2013 (UTC)
Doesn't the admin rather mean, that it's horrifying that the user's workaround does not work anymore, and not, that he considers the workaround itself horrible? --126.96.36.199 10:43, 13 August 2013 (UTC)
- No for sure he finds it horrifying that some user would use an error that could overheat the system as a way to "press" ctrl key. --Kynde (talk) 14:33, 29 April 2015 (UTC)
"std::cin no longer overheats the CPU when you hold down spacebar" from here. I chuckled when I was reading this. Maybe there are references buried in the comments, too. 188.8.131.52 21:11, 25 May 2015 (UTC)
- It does. A user called JB said "Although please can you implement an option to reinstate the cpu heating when space bar is pressed feature though, as I have code that relies on this feature."