The final character suggests the utterly surreal idea of using butterflies; he is just using the Butterfly effect, a "phenomenon whereby a minor change in circumstances can cause a large change in outcome". Emacs is known for having a large number of add-ons to perform all sorts of functions beyond simple text editing. These commands are usually referred to by the key sequence required to activate them, such as "C-x M-c"(Control-x Meta/Esc/Alt-c, though this exact key sequence is a bit different from most Emacs commands and could be a joke or typo). The macro referenced is a pun on the play/movie titled "M. Butterfly". Later versions of Emacs actually added a "M-x butterfly" command as an Easter-egg youtube demo, screenr demo.
To cap this the title text suggests manipulating the universal constants to get the required data onto the disk. I.e. the only real programmer is the creator of the universe - see 505: A Bunch of Rocks.
I was going to edit the above description, but it was taking too much time to edit it into a suitable format, so here's the long version.
In the beginning was UNIX. And it was good. And it was written by some very clever people.
One of the first very useful tools they wrote was ed, a "line-editor" (i.e. it works one line at a time). It uses some simple commands, and was created to work on very-old-school teletype machines, where you type a command, and ed types a response back.
It was a lovely bit of code. Using very little the way of resources, it allowed you to create a text document of any length, including source code in whatever language you wanted to program in.
Eventually, a more sophisticated version called ex (short for EXtended) was written by a clever man named Bill Joy. While it has some great improvements over ed, it was still a line-editor.
The trouble was, using a line-editor like ed or ex requires you to have a very good mental model of the document you are creating. Unfortunately, humans aren't very good at this, so they constantly need to refresh their mental model by printing out big chunks of the document (or program) they are working on. This took a LOT of paper using teletypes.
Eventually, teletypes were replaced with terminals. This saved a lot of paper. But the people who created the terminals began making them smarter than teletypes, so that magic character sequences could be used to move the cursor around, rather that simply going character-by-character across the line, then scrolling down to the next line, and so on. This opened up a whole new world.
The very clever Bill Joy took advantage of these magic character sequences to create his wonderful "full-screen" text editor vi. vi was the "VIsual mode" of ex. With vi, the user could see a screen-full of text at once. Entire forests were saved.
Emacs was developed at the same time as vi, using the same magic characters, and was also a full-screen text editor. I've never used it, so I can't speak to its merits, but there are many people who still find it more useful than any GUI they've tried.
On the one hand, vi and emacs are more sophisticated tools, and thus take longer to learn to use than ed. However, once you learn to use them, they make writing code EASIER, and they are therefore considered a less praise-worthy way of writing code by those concerned with defining what a "Real Programmer" is. (In other words, those programmers suffering from testosterone poisoning.)
Using cat to write a program looks like this: (Note that the $ is the prompt provided by the computer. The rest is typed by the user. And the ^D means the user held down the control key while typing the letter "d".)
$ cat | cc
The user types C code here, and ends with ^D. Assuming all goes well, the compiler silently finishes after creating the executable program a.out in the user's current working directory.
The reason this is considered a more praise-worthy way of coding is that, in those early days, doing this meant that your code was lost the instant you typed it. If you made a mistake, you would have to type the whole thing again. So doing this for code of any sophistication was considered an act of courage, confidence, and conviction. (I myself did it several times, for the fun of it, when no-one was watching, though never for a program that took more than about 30 lines of code. I was delighted that it worked all 3 times, but since I love to write re-usable code, this wasn't really something I wanted to keep doing.)
NOW PAY ATTENTION. VI IS NOT VIM! Vim was written in 1991, long after more sophisticated shells were created that made it possible to copy and paste text from one part of the screen to another. This ability greatly reduced the risks of using cat to pass your source code directly to the compiler, so it was no longer a praise-worthy stunt. Thus the line "Real programmers use vim" was NEVER considered true by any UNIX programmer.
Whether this was a mistake of the author, or the character (possibly Megan?) is unclear. It seems possible that it was a simple typo, but since I've never seen one in the strip before, I'm somewhat skeptical.
--MisterSpike (talk) 07:12, 17 June 2013 (UTC)
cat | cc doesn't work on my system. My
cc is simply a symlink to
gcc; what's yours? --Lucaswerkmeister (talk) 10:16, 7 August 2013 (UTC)
- One can also use
- $ cat | gcc -xc -
- The program will be an a.out file. 188.8.131.52 (talk) (please sign your comments with ~~~~)
I would never claim to be an emacs expert, but I'm reasonably proficient in it. Command of the form M-x (whatever) are a way of calling commands (or, really, arbitrary functions in the emacs code) by name. SO 'M-x butterfly' means that there is a function named "butterfly" somewhere, but that it has not been assigned a keyboard shortcut (or it has, but you're calling it the long way).
Also, three are still advanced Linux programmers today who swear by vim or emacs being superior to IDEs. There are specific technical reasons for this: emacs is basically an IDE construction kit that's incredibly easy to extend and customize, and is more customizable than pretty much any other program in the history of software with the exception of a Smalltalk installation. And vim has highly evolved commands to give experts a superhuman typing and editing speed when coding.
So when someone claims that "real programmers use vim," they are claiming that RIGHT NOW, vim is the best possible editor for developers of sufficient competence. There's a community of very smart people that basically thinks this.
Tess (talk) 04:19, 15 December 2013 (UTC)
What is "Meta"? As in "M-butterfly"?184.108.40.206 23:20, 27 April 2015 (UTC)
When I read this, I started up emacs and tried this... until I realized that there was no butterfly key... --220.127.116.11 00:51, 13 May 2015 (UTC)
"Meta" is binded to "Alt" in modern keyboard. "Meta" is referring to the "Meta" key in early LISP keyboard. --18.104.22.168 18:58, 19 May 2015 (UTC)
I assume this cartoon was inspired by an earlier User Friendly cartoon, in which Miranda ends an editor one upsmanship discussion by saying: "Well, I edited the inodes by hand. with magnets." See also this classic Dilbert cartoon. Espertus (talk) 21:56, 13 August 2015 (UTC)
Real programmers don't use any negative calls to sqrt(), of course. --22.214.171.124 22:07, 7 September 2015 (UTC)
August 1984 "Real programmers use cat as their editor." http://web.cecs.pdx.edu/~kirkenda/joy84.html --126.96.36.199 00:21, 18 October 2015 (UTC)
Could the title text be a reference to the novel "Heechee Rendezvous" by Frederik Pohl, in which an alien species causes the universe to start to contract, in order to provoke a new Big Bang which would lead to "improved" natural constants? --188.8.131.52 09:37, 2 December 2015 (UTC)
The title text is more likely a reference to the end of the book "In the Beginning Was the Command line", where programming / simulation develops to creating worlds on a single command line, specifying natural constants (in all their precision). Hrabbey (talk) 13:23, 30 March 2018 (UTC)
There has been a community portal discussion of what to call Cueball and what to do in case with more than one Cueball. I have added this comic to the Category:Multiple Cueballs. In this comic it cannot be said clearly that any of the four/five (if the guy with the buttefly in hand is not the same as the one speaking off-panel about it) is more correctly called Cueball than any of the others. But typically the one named Cueball is either the protagonist or the one with the interesting parts, or the one with the punch line. In this comic it would be the e-mac Cueball, as he makes the butterfly guy loose out to e-mac. It may thus be OK to list him as Cueball, and the others as something else. So I changed that some time ago in the explanation, and transcript. But then I also made sure that it was clear that the other guys also looks like Cueball. --Kynde (talk) 21:20, 20 December 2015 (UTC)
Real Programmers use MS Paint: http://i.imgur.com/QlGpd.gif Luc (talk) 01:40, 3 July 2016 (UTC)