Go to this comic explanation
|| This explanation may be incomplete or incorrect: Created by a SPREADSHEET. Has a lambda function just been added to excel at the time this computer came out? Why is Ponytail pleased, what will she use it for, that she could not before? Another reference to a law/hypothesis about computing? Please mention here why this explanation isn't complete. Do NOT delete this tag too soon.|
Cueball is computing and Ponytail criticizes him in a way that is reminiscent of the Code Quality series, although not as harsh. Cueball has lots of strange computer problems, and this will most likely result in another one.
The comic begins with Ponytail finding out that Microsoft Excel is adding a lambda function to their function library. A lambda function is a temporary function created inside another function that completes a repetitive task that is too unimportant to code a named function for. They are commonly found in programming languages such as Lisp, Python, and many others. A lambda function is also called an Anonymous function because in most languages it can be passed to other functions (including another lambda function) without needing to be given any formal name during coding, or given 'closure' under whatever name(s) its calling procedures desire.
Finding that Excel is adding a lambda function pleases Ponytail. Cueball claims that the lambda function is unnecessary, as when he needs arbitrary computation he just adds a block of columns to the side of his sheet and has a Turing machine process it. This would technically work as a lambda function but would be rather difficult to construct and maintain.
Ponytail finds his solution absurd and is convinced Cueball is "doing computing wrong". But he claims that all computing is equally wrong, citing the Church-Turing thesis, a hypothesis which says that a function can be computed by executing a series of instructions if and only if that function is computable by a Turing machine. A classical Turing machine uses an infinitely long strip of tape as its memory; for Cueball, the large Excel column acts as the "tape". All ways of computing are "equally wrong" since, according to this thesis, they can all be translated to or from a Turing machine.
Ponytail and Cueball appear to have different ideas of 'computing'. Ponytail, like most programmers, probably includes efficiency and readability as important characteristics of 'doing computing right'. Cueball appears interested only in computability, a more theoretical point of view than Ponytail's.
Ponytail then says that Turing would change his mind if he saw Cueball's spreadsheet, presumably because of the extreme complexity of Cueball's code in the spreadsheet. Cueball's final statement is that Turing could ask him to stop, but would not be able to prove if he actually will stop.
Cueball's final statEment is a reference to the halting problem mentioned in the title text. It is the problem of determining whether a given Turing machine will halt. The problem has been shown to be undecidable, i.e., there exists no algorithm that computes whether an arbitrary Turing machine will halt or not. Because of the way Cueball has behaved, he has been specifically mentioned in Turing's later formulations of the halting problem. Cueball finds this very rude. This is of course a joke, since Turing has been dead since 1954, presumably long before Cueball was born. But it would be crazy indeed if a scientist became so mad at a person that he would mention this person by name in his formulation of a serious problem.
Over-complicated spreadsheets were also mentioned in 2180:Spreadsheets.
An example of a lambda function:
list(map(lambda a: a + 1, [1, 2, 3])) # -> returns [2, 3, 4]
Here, each element of the array with values 1,2,3 is treated in succession as a variable 'a' that is incremented by one, to produce values of 2,3,4 which are then reconstructed as a list for output.
A recursive lambda might be:
# If current value (x) is evenly divisible by 4, return the source (v) * current (x)
# Otherwise, print current, and then try the process again with the current value of x + 3
r = lambda x: x * v if x % 4 == 0 else print(x) or r(x + 3)
pointless_recursion(12) # returns 144 (i.e., 12*12)
pointless_recursion(11) # prints 11, 14, 17 then returns 220 (i.e., 20*11)
In this instance, the function is given the name 'r', and features a (conditional) call back to this self-same 'r' within it. The 'x' is whatever value is the latest passed to 'r', while 'v' is that which was first passed to the container function.
Ideally, such techniques should be used to reduce Spaghetti code, not increase it. But this isn't a foregone conclusion, especially in Cueball's hands.
- [In a narrow panel, Ponytail is walking in from the left, looking down at her phone]
- Ponytail: Oh cool, Excel is adding a lambda function, so you can recursively define functions.
- [Ponytail, holding her phone to her side stands behind Cueball, who is sitting in an office chair with a hand on a laptop standing on his desk. He has turned around to face her, leaning with the other arm on the back of the chair.]
- Cueball: Seems unnecessary.
- Cueball: When I need to do arbitrary computation, I just add a giant block of columns to the side of my sheet and have a Turing machine traverse down it.
- [In a frame-less panel Ponytail is standing in he same position behind Cueball, who has resumed working on his laptop with both hands on the keyboard.]
- Ponytail: I think you're doing computing wrong.
- Cueball: The Church-Turing thesis says that all ways of computing are equally wrong.
- [Ponytail is still behind Cueball, who has a finger raised in the air, and the other hand is on the desk. Cueball's head has a visible sketch layer which has not been erased.]
- Ponytail: I think if Turing saw your spreadsheets, he'd change his mind.
- Cueball: He can ask me to stop making them, but not prove whether I will!
- In the original version of the comic, in the final panel, there was a gray pencil outline, slightly different to Cueball's head that had not been removed.
- This was later fixed in a re-upload.
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.