Live data from Hacker News

Omniref (YC W15) Is Rap Genius for Code

techcrunch.com

1–10 of 27 posts

Re: Omniref (YC W15) Is Rap Genius for Code

#3

really cool idea - i have always loved the backbone/underscore/coffeescript code documentation - hope there is more of this to come

Thanks...there is! We've got something you'll like coming Real Soon Now. Email me (tim@omniref), and I'll get you on the beta list.

Re: Omniref (YC W15) Is Rap Genius for Code

#6
wow this is great!

a 6-7 months ago, as a side project (which I never got around to finishing) I was trying to build was something like this. Actually, when I pitched the idea to my friends, the line I used was "rap genius for code". (was trying to annotate huge open source projects like the linux kernel) So the second I saw this post the first words I said to myself were "fuck! I should have finished it". But this is great!

Re: Omniref (YC W15) Is Rap Genius for Code

#8
What sorts of stuff do you guys have planned for indexing methods?

It looks like right now there's full text search which is already really useful. I'd be really interested to see some more structured search based on the AST of the code for example. Hoogle is a really good example of something similar for Haskell, admittedly that relies heavily on the strongly typed nature of Haskell and probably won't work for Ruby.

Very cool stuff guys.

Re: Omniref (YC W15) Is Rap Genius for Code

#10
post #8

What sorts of stuff do you guys have planned for indexing methods? It looks like right now there's full text search which is already really useful. I'd be really interested to see some more structured search based on the AST of the code for example. Hoogle is a really good example of something similar for Haskell, admittedly that relies heavily on the strongly typed nature of Haskell and probably won't work for Ruby.…

We do a lot of custom tokenizing, indexing and scoring logic right now to (for example) make method name searches work like you'd expect: you can (mostly) search for a common method name in activerecord, and the right thing will come up, as opposed to one of the many different forks. This is a constant game of whack-a-mole for us.

That said, we have more features planned than time to implement them...we've got a method-body search working internally, but we're not yet happy with the quality of the results. We'd definitely like to do something with signals coming from the AST to improve that. We also have signals in place to help rank based on usage across all the code we know about, but those could be a lot more robust. We're also going to be doing a pass in the near future to deal with some noisy results that have been leaking in since we opened up to all GitHub repositories.

We're open to suggestions, though...do you have an example of something you'd like to see us implement?

Post reply on HN