Live data from Hacker News

Our new search index: Caffeine

googleblog.blogspot.com

61–70 of 82 posts

Re: Our new search index: Caffeine

#61

Earlier quoted context omitted.

I'd have to disagree. It shows us that Google has adopted the experimental "Bohr" model of database indexing.

I'm not sure if I get this...is this just a pithy one-liner, or am I missing something deeper here?

http://en.wikipedia.org/wiki/Bohr_model

The right hand side of the diagram....

So you were right about the "pithy one liner".

Re: Our new search index: Caffeine

#62

Earlier quoted context omitted.

I'm not sure if I get this...is this just a pithy one-liner, or am I missing something deeper here?

http://en.wikipedia.org/wiki/Bohr_model The right hand side of the diagram.... So you were right about the "pithy one liner".

Then this comment should be flagged. It (a) reduces the intelligence of the discussions on HN (b) pushes more worthy comments down below the fold, (c) encourages similar pithy comments, and (d) makes those who would otherwise make intelligent comments less likely to comment.

This is the kind of one-liner that perhaps Jon Stewart would make...and while there is nothing wrong with The Daily Show, I thought that we, the HN community, are collectively better than that.

Sorry for the rant, but I'm just sick of wading through pithy one-liners on HN.

Re: Our new search index: Caffeine

#63
post #56

What I dislike about Google's current algorithm is that when I search for a common term such as "javadoc simpledateformat", the API documentation for Java 1.4.2 (as opposed to 1.6) comes up as apparently, that is what most documents on the web link to. I hope this new index will allow more recent and more up-to-date documents to get to the top of the results list.

In Firefox I have the following quick-search to fix that (and make searching the API a little faster):

http://www.google.com/search?q=java+6+%s&ie=utf-8&oe...

This should also work in Chrome.

Re: Our new search index: Caffeine

#65
post #43

Posted by Carrie Grimes, Software Engineer Dr. Grimes currently leads a research & technical team in Search Infrastructure at Google and is actively trying to figure out what criteria make a search engine index "good," "fast," and "comprehensive." Yeah, right. "Software Engineer" ? bullshit.

"Software Engineer" is a generic title at Google; the actual role can vary wildly. Carrie is an impressively talented engineer and statistician.

Re: Our new search index: Caffeine

#66
post #56

What I dislike about Google's current algorithm is that when I search for a common term such as "javadoc simpledateformat", the API documentation for Java 1.4.2 (as opposed to 1.6) comes up as apparently, that is what most documents on the web link to. I hope this new index will allow more recent and more up-to-date documents to get to the top of the results list.

In Firefox I have the following quick-search to fix that (and make searching the API a little faster): http://www.google.com/search?q=java+6+%s&ie=utf-8&oe... This should also work in Chrome.

Yep, I've done exactly that for the Java 6 docs in Chrome and FF. The general point of how do you keep the latest version of a set of documents the most relevant still applies however. I hope Google can fix this :)

Re: Our new search index: Caffeine

#68

Earlier quoted context omitted.

http://en.wikipedia.org/wiki/Bohr_model The right hand side of the diagram.... So you were right about the "pithy one liner".

Then this comment should be flagged. It (a) reduces the intelligence of the discussions on HN (b) pushes more worthy comments down below the fold, (c) encourages similar pithy comments, and (d) makes those who would otherwise make intelligent comments less likely to comment. This is the kind of one-liner that perhaps Jon Stewart would make...and while there is nothing wrong with The Daily Show, I thought that we, the…

I felt a small amount of humor -- indeed, what a small attempt it was, I didn't consider it that amusing -- was welcome in the thread discussing the shortcomings of the accompanying infographic. Unless you'd like to have a serious discussion about the shortcomings of the accompanying infographic? I'm not sure there's much intelligence to be had in a discussion responding to "Wow is that ever a terrible infographic".

Can we discuss its poor choice of color? Its lack of visual appeal? The obvious selection of a Home Depot paint swatch to represent Google's old index, and what that means for their database technology? Not really. Not in response to "Wow is that ever a terrible infographic".

I'd be hesitant to flag everything that you don't initially understand. Cut HN some slack, we're intelligent people and we enjoy humor as much as the next man. I certainly appreciate when someone makes me chuckle in the comments, and I'd loathe HN if that went away by your hand.

Given something like http://news.ycombinator.com/item?id=1403672 is it HN that has to change, or the person in the chair? I realize your time may be valuable, but you don't have to read everything and get offended by its presence -- including my comment.

Re: Our new search index: Caffeine

#69
post #59

Earlier quoted context omitted.

Google uses only four languages in their codebase: C++, Java, Python and Javascript. Yegge has covered this pretty extensively in the past. Go Google him.

And Go, presumably.

I asked what this project was probably written in...

Re: Our new search index: Caffeine

#70

Earlier quoted context omitted.

http://en.wikipedia.org/wiki/Bohr_model The right hand side of the diagram.... So you were right about the "pithy one liner".

Then this comment should be flagged. It (a) reduces the intelligence of the discussions on HN (b) pushes more worthy comments down below the fold, (c) encourages similar pithy comments, and (d) makes those who would otherwise make intelligent comments less likely to comment. This is the kind of one-liner that perhaps Jon Stewart would make...and while there is nothing wrong with The Daily Show, I thought that we, the…

Wow. It's okay you didnt get it, guy.
Post reply on HN