Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

What if programming languages were methods to eat an orange?

C: you forgot to add a zero-terminator and accidentally ate your table.

C++: You wish to start peeling the orange, but arranged on the table are thousands of different knives. Each one can help peel the orange but no matter what knife you choose, supporters of the other knives will tell you you're peeling the orange wrong.

Objective-C: You peel your orange, meanwhile sending messages to your OrangePeelingDelegate about your progress. Once you're finished peeling it, your OrangePeelingDelegate tells you to eat the orange.

Ruby: Install the Orange gem. Bash your head as the native extensions don't compile. Install liborange-devel, and recompile. Then simply peel orange, and eat it.

MIX Assembly: You don't actually have an orange, but luckily you have a very nice, streamlined model of one. You find it's best to study the orange in hypothetical terms instead of actually eating a real orange.

Haskell: You prepare to eat infinite oranges. You then eat only the first.

JavaScript: you rip off a peel with ease, cut orange into slices and pick one in anticipation. Your orange turned out to be a lemon. Because, your knife can only cut lemons.

Prolog: Yes.

XML: You found and want to eat an orange orange orange that you want to eat because you found it


Reposted fromnordern nordern viatatonka tatonka

Don't be the product, buy the product!