4 ms·
Oh, thanks for posting this! I'm the author (and one of the co-creators of Sourcegraph at https://sourcegraph.com https://sourcegraph.com), and I'm happy to ans
by sqs 12y ago
Oh, thanks for posting this! I'm the author (and one of the co-creators of Sourcegraph at https://sourcegraph.com https://sourcegraph.com), and I'm happy to answer any questions anyone has here.
- knodi 12y agoWhat made you/your team decide to do this in Go?
- sqs 12y agoWe chose Go because it offers amazing facilities for introspecting its own source code, such as go/doc (http://golang.org/pkg/go/doc/ http://golang.org/pkg/go/doc/ and https://sourcegraph.com/code.google.com/p/go/.GoPackage/go/doc/.def/New https://sourcegraph.com/code.google.com/p/go/.GoPackage/go/d...) and go/types. So, it was the obvious choice to use to prototype Sourcegraph. The reputation of the core team and our initial experience learning it were also factors.
- viciousplant 12y agoCan you share the technology & methods sourcegraph use for syntax/semantic analysis? If there is a brief comparison of tools you have tried and abandoned it would be really really helpful. The accuracy of whatever working behind the scene is simply amazing.
- sqs 12y agoYeah, it's almost all open source now and we're releasing the last bits (plus the coordination code) between now and next week. We will post another article when it's ready next week. Email me at sqs at sourcegraph.com in the meantime if you are too curious to wait. :)