sqs

36 ms·

361.
by sqs 9y ago
Sourcegraph CEO here. The Sourcegraph Editor features (on https://about.sourcegraph.com/products/editor , plus other things on the roadmap that aren't on that page) are currently not possible to build as an extensi
362.
by sqs 9y ago
Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions here. We're really excited to start helping with the code editing and review workflow as well.
363.
by sqs 9y ago
The reason is that they broke it down by MSA: https://en.wikipedia.org/wiki/List_of_Metropolitan_Statistic... . Palo Alto and nearby cities are in the San Jose-Sunnyvale-Santa Clara MSA.
364.
by sqs 9y ago
Sourcegraph founder here. We love it. The more developers who are using code intelligence in their tools, the better the language support will be for all the various languages and repositories out there. That's good for developers ever
365.
by sqs 9y ago
Sourcegraph founder here. The Chrome extension direct link is https://chrome.google.com/webstore/detail/sourcegraph-for-gi... . Thanks for the mention!
366.
by sqs 9y ago
Nope. What kind of specific criteria were you thinking? Any country, timezone, etc., is OK.
367.
by sqs 9y ago
Thanks for posting this. We'll think about how we can make that search UX clearer. And when we have C/C++ support, I hope you'll find it super useful.
368.
by sqs 9y ago
We built Sourcegraph, which is a web-based code search and navigation tool. Our Python support is in beta, and you can try it out at https://sourcegraph.com/github.com/plotly/dash/-/blob/dash/d.
369.
by sqs 9y ago
A JIRA installation with 2,000 users probably has many fewer developers, and you'd only pay for Sourcegraph for developers. For customers where this makes a big difference, we work with them on the pricing. But if you're a large c
370.
by sqs 9y ago
We've found LSP pretty easy to extend for our purposes, without any explicit help from the protocol. Check out the `extension-*.md` files at https://github.com/sourcegraph/language-server-protocol for our extensio
371.
by sqs 9y ago
Thanks for the report. We'll fix this asap.
372.
by sqs 9y ago
> But isn't that exactly the point of the post? The approach is nice for editors but unsuitable for IDEs. Yep. I'm just giving my thoughts on what it'd take to extend LSP so it addresses the issues raised in the blog post.
373.
by sqs 9y ago
Completely agree. But the tools don't make this very easy. Back in college I was working on patches to OpenSSL, Chrome, Firefox, Apache, etc., to add support for TLS-SRP, and it was a huge pain to jump into these massive codebases and
374.
by sqs 9y ago
Interesting post. I have worked a lot with LSP personally and professionally. I'm CEO of Sourcegraph, and we use LSP everywhere. (Go to https://sourcegraph.com/github.com/mholt/caddy/-/blob/cadd
375.
by sqs 9y ago
Sourcegraph CEO here. There are a ton of keyboard shortcuts, and they (mostly) match VS Code's default ones. To see them all, hit Shift+Cmd+P (or Shift+Ctrl+P), and go to 'Preferences: Open Keyboard Shortcuts'. Here are some
376.
by sqs 9y ago
Yep, I just uploaded it as a Gist. We'll put this up on the site soon as well. https://gist.github.com/sqs/2a2680eff4dad159ae754756fe9326c2
377.
by sqs 9y ago
Thanks. I appreciate the feedback and completely agree. We will have a FAQ up tomorrow.
378.
by sqs 9y ago
We're a small team and we don't yet update the Firefox extension as frequently (it is still a manual process, whereas we've automated the deployment of our Chrome extension). That's all. Regarding the licensing, I meant
379.
by sqs 9y ago
We're working on improving that, and it'll work well for Python when we officially support Python. See https://news.ycombinator.com/item?id=14261611 for why, if you're curious.
380.
by sqs 9y ago
Before this, we were using a little bit less of VS Code. Before that, we had a much more minimal but custom frontend.
381.
by sqs 9y ago
Thanks. I am on your side and have been a Ruby fan since 2005. I'm trying to throw money at building better Ruby tooling. :) I'm familiar with those projects, but when I last tried them, they did not work well enough with some add
382.
by sqs 9y ago
Got it. I'll email you. I would love to learn more about how you read code on mobile.
383.
by sqs 9y ago
Sourcegraph CEO here. There are indeed some glitches in syntax highlighting, on other languages as well. I hope it doesn't significantly detract from the product value, but I understand it is not good. Here's why it's happeni
384.
by sqs 9y ago
Thanks! The next languages will be TypeScript, JavaScript, Swift, and Python. You'll see some TS and JS support in the Chrome extension already. If you want to shoot me an email at sqs@sourcegraph.com, I'll make sure you hear abou
385.
by sqs 9y ago
We do have an API available to customers running Sourcegraph internally. We plan to open it up to users of Sourcegraph.com in the future, but I don't have a date for that. In the meantime, URLs like the following will stay around forev
386.
by sqs 9y ago
Thanks for the feedback. We haven't done much mobile-specific work, and Sourcegraph does not work well on mobile. (Unlike most sites, very few people actually use Sourcegraph on mobile, but we want to make a great first impression no m
387.
by sqs 9y ago
Sourcegraph CEO here. We don't support Ruby yet, unfortunately. It officially works for Go and Java, and we have alpha/beta support for a couple more languages enabled too (TypeScript and JavaScript). As you can imagine, Ruby code
388.
by sqs 9y ago
Sourcegraph CEO here. We have a Firefox extension at https://addons.mozilla.org/en-US/firefox/addon/sourcegraph-a... , but it does not have quite as many features as the Chrome one. I agree we should open-sour
389.
by sqs 9y ago
Whoops, F1 or or Ctrl+E on Windows. Just updated the post above.
390.
by sqs 9y ago
Sourcegraph CEO here. We're on it. We are seeing significantly increased load times for some users due to a bottleneck in our serving of Git data. Sorry about the issues...will be fixed asap. Edit: Fixed. Thanks!

More ›