Main Page

Explain xkcd: It's 'cause you're dumb.
Revision as of 11:21, 8 April 2013 by Davidy22 (Talk | contribs)

Jump to: navigation, search

Welcome to the explain xkcd wiki!

We have collaboratively explained 1483 xkcd comics, and only -4 (-0%) remain. Add yours while there's a chance!

Latest comic

Go to this comic explanation

Troubleshooting
"Oh, you're using their Chrome APP, not their Chrome EXTENSION. They're very similar but one handles window creation differently." is a thing I hope I can stop saying soon.
Title text: "Oh, you're using their Chrome APP, not their Chrome EXTENSION. They're very similar but one handles window creation differently." is a thing I hope I can stop saying soon.

Explanation

Ambox notice.png This explanation may be incomplete or incorrect: Created by a FEMBOT - Please change this comment when editing this page.

The humor of this comic revolves around the fact that due to complexity and somewhat low quality of the modern software, the reasons for many problems that users experience (and possible solutions) are not obvious and straightforward and methods for repairing the problem often rely on invoking certain seemingly irrelevant actions that happen to cause a desired side-effect. As the author points out, knowing these non-obvious ways to repair the problems requires memorization of lots of "stupid computer knowledge" rather than relying on logic and understanding of general principles of software. By "stupid", of course, he means "seemingly irrelevant".

In many cases, Randall (or Cueball as his avatar) loves to help people using his specific knowledge (see 208: Regular Expressions). But when the trick is "stupid", he would prefer the programmers to fix the problem definitely so he never has to rely on this trick anymore.

One particular scenario that is used as an illustration of such illogical way to repair the problem with the software is depicted in the comic. Here, two users are attempting to resolve the problem of lack of response from the software application despite attempts to click on any elements of it. A suggestion is made that this is not due to abnormal behavior of the software ("freezing"), but rather because either the user or the software itself has opened a modal dialog window with coordinates outside of the main screen area, where it can not be seen. Modal dialog windows in desktop operating systems by design get the sole focus of the user input when launched, blocking access to the rest of the application window. They are valid GUI tools and are used when the software needs user's input before it can proceed further. However, opening such window and placing it outside of the visible screen area ("offscreen") will make the window both inaccessible and invisible to the user, precluding him/her from closing it and re-gaining access to the software. One non-obvious way to repair such problem is to switch the screen resolution outside of the program experiencing the problem (using operating system configuration tools) to some other resolution not normally used and then switch the resolution back to normal. Switching the resolution in itself does not fix the problem because most often the highest resolution is normally being used so one can rarely switch to higher resolution to gain access to the modal dialog stuck in "offsceen" area. Instead, the fix relies on the fact the in many desktop operating systems the resolution switch also forces the operating system to redraw all windows on the desktop (which in itself is a logical and normal action) and, while doing so, some operating systems will also reevaluate the appropriateness of the coordinates of all windows and adjust them so that they are do not end up in off-screen area after the resolution change. The latter is also a logical action and prudent by the operating system, however, in our scenario it is used as a side-effect to fix the problem. This is due to the fact that the operating systems rarely provide other, more obvious ways to bring the off-screen windows back to the visible area.

Transcript

Ambox notice.png This transcript is incomplete. Please help editing it! Thanks.



Is this out of date? Clicking here will fix that.

New here?

Last 7 days (Top 10)

Lots of people contribute to make this wiki a success. Many of the recent contributors, listed above, have just joined. You can do it too! Create your account here.

You can read a brief introduction about this wiki at explain xkcd. Feel free to sign up for an account and contribute to the wiki! We need explanations for comics, characters, themes, memes and everything in between. If it is referenced in an xkcd web comic, it should be here.

  • List of all comics contains a complete table of all xkcd comics so far and the corresponding explanations. The red links (like this) are missing explanations. Feel free to help out by creating them! Here's how.

Rules

Don't be a jerk. There are a lot of comics that don't have set in stone explanations; feel free to put multiple interpretations in the wiki page for each comic.

If you want to talk about a specific comic, use its discussion page.

Please only submit material directly related to —and helping everyone better understand— xkcd... and of course only submit material that can legally be posted (and freely edited.) Off-topic or other inappropriate content is subject to removal or modification at admin discretion, and users who repeatedly post such content will be blocked.

If you need assistance from an admin, feel free to leave a message on their personal discussion page. The list of admins is here.

Personal tools
Namespaces

Variants
Actions
Navigation
Tools

It seems you are using noscript, which is stopping our project wonderful ads from working. Explain xkcd uses ads to pay for bandwidth, and we manually approve all our advertisers, and our ads are restricted to unobtrusive images and slow animated GIFs. If you found this site helpful, please consider whitelisting us.

Want to advertise with us, or donate to us with Paypal or Bitcoin?