Google Code Search Reveals Dark Corners
saccade.com writes, "The new Google Code Search isn't just for hackers sniffing for passwords. Jason Kottke and friends have discovered the new feature reveals all sorts of dark corners hidden in our code. And you thought nobody ever read your comments!" From the article: "Code search is a great resource for web developers and programmers, but like the making available of all previously unsearched bodies of information, it's given lots of flashlights to people interested in exploring dark corners."
Google seems to inspire this kind of behaviour for some reason. The have been lots of websites like krugle who search a big db of code, and these things didn't come up until google launched this.
Indeed!
Moderator hint: a comment is neither "Flamebait" nor "Troll" if it is true.
"it's given lots of flashlights to people interested in exploring dark corners."
They say sunshine is the best disinfectant. More eyeballs can fix problems as well as exploit them.
Paleotechnologist and connoisseur of pretty shiny things.
"Windows Sucks"
--
Go Where Web Thinkers Gather
Watch the Teaser Trailer for "The Lightning Thief" Her
Zork nostalgia, anyone?
Paleotechnologist and connoisseur of pretty shiny things.
Ten pages of righteous anger
It also inspired Number of fucks per programming language and license.
This is a fairly amusing one.
I like the memset search on that page too... scary. People need to run Lint or something. (Will Lint pick up that error?)
All your base :-D
I was not drunk when I wrote this; that's just some immature coder making fun of me.
Granted, being drunk is about the only valid excuse I could make for only initializing half of a doubly-linked list node . . .
Who said programming was easy? http://google.com/codesearch?hl=en&lr=&q=%22kill+m e+now%22
This is my favorite from the article: The phrase "should be big enough" should never be seen alongside statically allocated arrays.
How long before SCO files a third amended counterbrief to IBM's second interrogary motion for relief claiming new evidence of infringement after one of their marketing boys tries 'Linux Santa Cruz Operation' after reading about Google Code in the WSJ?
.sig: Now legally binding!
See here for an explanation (from the horse's mouth, as it were...)
1. Read Slashdot
2. Search Google Code
3. ???
4. Profit!
You incult clod, if the GP said it it was because the GGP's sig is a reference to a painting of an apple that says "Ceci n'est pas une pomme" ("This is not an apple") because it's not an apple but really a painting. The GP was pointing that the GGP's sig was actually a signature although it claimed not to be one, and thus that it didn't fit the spirit of the painting it was refering to, and that it would have been more like the spirit of it if instead of having it to be an actual sig, it was something he pasted at the end of every of his posts to make it look like a sig. It would look like a sig, but it wouldn't be one.
You just got troll'd!