How Google Code Search Worked (2012)

Re:How Google Code Search Worked (2012) by rkhassen9 on Thursday March 12, 2020 @02:32AM (#22554341)

Code search was “too good to be true, gotta pinch myself” awesome. I miss it to this day.

Here is how I used it - I’d type in some code I was working on and the search result would show similar code and how it was used. Great for debugging and thinking by looking at similar solutions. Sigh.

[ Parent | on HN ]

Re:How Google Code Search Worked (2012) by tehlike on Thursday March 12, 2020 @03:05AM (#22554487)

For me it was f:cc$ f:contentads some keyword I wanted to learn more about. Then a bunch of cross refs.

[ Parent | on HN ]

Re:How Google Code Search Worked (2012) by londons_explore on Thursday March 12, 2020 @06:54AM (#22555478)

You can still play with it here: https://cs.chromium.org/

[ Parent | on HN ]

Re:How Google Code Search Worked (2012) by fzzfff on Thursday March 12, 2020 @07:44AM (#22555754)

wow this site is so laggy, even on chromium

[ Parent | on HN ]

Re:How Google Code Search Worked (2012) by londons_explore on Thursday March 12, 2020 @05:32PM (#22562003)

Google engineers have superfast high end desktops and laptops, and 10 gbit internet connections. They don't tend to optimise their internal tools for low spec machines or internet connections.

[ Parent | on HN ]

Re:How Google Code Search Worked (2012) by hangtwenty on Thursday March 12, 2020 @11:09AM (#22557633)

Maybe you saw it but no need to sigh anymore:

https://news.ycombinator.com/item?id=22551856

https://opensource.google

[ Parent | on HN ]

Re:How Google Code Search Worked (2012) by j_knowles on Thursday March 12, 2020 @07:47AM (#22555780)

This gives me so much nostalgia!

[ Parent | on HN ]