by Ben Orenstein
Turns out Google is now crawling through source code. The GoogleBot, in its never-ending quest for sentience, searches inside tars, zips, and even dives into CVS and Subversion repositories. As Code Search is targeted at programmers, you can perform fantastically powerful queries using POSIX extended regular expressions.
In tribute to the valiant struggles of coders everywhere, please enjoy:
The best in programming profanity
/* We will NOT put a fucking timestamp in the header here.
Every time you put it back, I will come in and take it out again.
I’m sorry. This field does not belong here. We fill it with a 0 so
it compares the same but is not a reasonable time. */
/* Boy, would I like to make the thing expire one second ago, or what? Of course I would. But that slimy, stinking, load of pig manure that is called Netscape/1.1N doesn’t pay any attention to the seconds part of the time… after all, what’s a second or two amongst friends? So, I thought to make it expire one minute ago, but naturally, that didn’t work on 1.1N either. Losers. So, I made it expire 24 hours ago, which, if you ask me, is most heinous, considering the Last-Modified date could be later than that. I fucking hate you, you monopolizing piece of Netscape feces. */
Fuck me gently with a chainsaw! Will someone please tell me how the fuck you resize a fucking widget?? Why, when I call whatever resize method I try with 64×64 does the fucking window end up 64×82? WHY???????? WHY???????? WHY???????? WHY???????? WHY???????? WHY???????? (why..?)
## aaahhh, user input. who would have though that such a simple
## idea would be SO FUCKING COMPLICATED?! because apparently
## Ncurses.getch (and Curses.getch), even in cbreak mode, BLOCKS
## ALL THREAD ACTIVITY. as in, no threads anywhere will run while
## it’s waiting for input. ok, fine, so we wrap it in a select. Of
## course we also rely on Ncurses.getch to tell us when an xterm
## resize has occurred, which select won’t catch, so we won’t
## resize outselves after a sigwinch until the user hits a key.
## and installing our own sigwinch handler means that the screen
## size returned by getmaxyx() DOESN’T UPDATE! and Kernel#trap
## RETURNS NIL as the previous handler!
## so basically, resizing with multi-threaded ruby Ncurses
## applications will always be broken.
## i’ve coined a new word for this: lametarded.
And my personal favorite:
(Links are to the original sources)
Stay tough out there guys. Happy Monday.