Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sqs
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
sqs
2y ago
Rule of law FTW! Governments can't usually promise timelines, but when the process is well documented and predictable, that is a very good thing.
32.
▲
by
sqs
2y ago
Cody is open source: https://github.com/sourcegraph/cody . And for the reasons explained there, it makes more sense for it to be open source.
33.
▲
by
sqs
2y ago
Yes, Cody can use Ollama for both chat and autocomplete. See https://sourcegraph.com/docs/cody/clients/install-vscode#sup... . This lets you use Cody fully offline, but it doesn't /prevent/ API
34.
▲
by
sqs
2y ago
Codium or Codeium? (Edit: Original post said Codium but it sounded like Codeium to me based on the description. :)
35.
▲
by
sqs
2y ago
Yeah, use this in your VS Code settings to use a different Ollama URL (here it's localhost:11434 but change apiEndpoint, model, and tokens to whatever). "cody.dev.models": [ { "provider": "opena
36.
▲
by
sqs
2y ago
Yes! Ollama models show up in the chat model dropdown in Cody, if Ollama is running on your machine.
37.
▲
by
sqs
2y ago
Not that many people use Copilot Chat, anecdotally. We've focused on codebase chat when building Cody ( https://cody.dev ), since we can use a lot of the code search stuff we've built before. It's hard to build, esp
38.
▲
by
sqs
2y ago
It's its own editor (albeit forked from VS Code), it's not a VS Code extension. They've built a great product.
39.
▲
Improving Cody Autocomplete: Faster and Smarter
(sourcegraph.com)
1 points
by
sqs
2y ago
|
0 comments
40.
▲
by
sqs
2y ago
Thanks for helping us make the product better! You can post any issues at https://community.sourcegraph.com . And you can also email support@sourcegraph.com (for customers or any private issues). We will continue to have a free t
41.
▲
by
sqs
2y ago
Cool! I’d love to chat.
42.
▲
by
sqs
2y ago
I was thinking business risk. Sorry it wasn’t clear.
43.
▲
by
sqs
2y ago
Fair, I probably didn’t hear from the devs who weren’t annoyed by that. I heard from plenty of devs who were annoyed by it.
44.
▲
by
sqs
2y ago
Both are factors, as I said in my original post (focus and risk).
45.
▲
by
sqs
2y ago
> So the reason these deals are now possible is mainly because time was freed up by not having the code base opensource? No, it's that if all the code is free and open source for anyone, we would not be able to charge for it and the
46.
▲
by
sqs
2y ago
Thanks for being a fan. And I understand it's a bummer to not have our code be public and open-source anymore. Sorry. It's a bunch of reasons that add up. I'll give some more details for anyone curious. (And I know that despi
47.
▲
by
sqs
2y ago
Awesome to hear! What sucks about Sourcegraph for you, and how can we make it better?
48.
▲
by
sqs
2y ago
Yes! We took a snapshot of the code and are keeping it at https://github.com/sourcegraph/sourcegraph-public-snapshot . I see the point about keeping the old repo name so that links work. That's also mentioned in th
49.
▲
by
sqs
2y ago
Sourcegraph CEO here. We made our main internal codebase (for our code search product) private. We did this to focus. It added a lot of extra work and risk to have stuff be open source and public. We gotta stay focused on building a great c
50.
▲
by
sqs
2y ago
Thanks! We appreciate you. It was really a focus thing. It added a lot of overhead, lost focus, and risk to have stuff be open source. Most customers weren't telling us it was valuable to them, and frankly we heard very little from peo
51.
▲
by
sqs
2y ago
Glad you use Sourcegraph! I remember that blog post and thought it was awesome. I am the Sourcegraph CEO, and we haven't changed anything about our public code search at https://sourcegraph.com/search . That's the
52.
▲
by
sqs
2y ago
We still have tons of repositories searchable at https://sourcegraph.com/search , almost a million. We did cull lots of non-GitHub repositories and repositories with less star. It was very complex to keep up with millions of
53.
▲
by
sqs
2y ago
Impressively fast responses from Points.com!
54.
▲
by
sqs
2y ago
1. Ah, this commit message feature isn't available in JetBrains yet, unfortunately. Most things carry over since they both use the same underlying code, but this is more editor-specific. 2. Your "reasonable near-term goal" is
55.
▲
by
sqs
2y ago
Not for this fine-tuned model yet, but Cody supports local models: https://sourcegraph.com/docs/cody/clients/install-vscode#sup... . I just used Cody with Ollama for local inference on a flight where the wifi
56.
▲
by
sqs
2y ago
Yeah, that is needed to make everything more accurate. We are working on 3 related things to make Cody better understand the structure of your code and take feedback from the compiler (and other tools). All are experimental and not enabled
57.
▲
by
sqs
2y ago
For 1, set `"cody.experimental.commitMessage": true` in VS Code and then click the Cody icon above the commit message box in VS Code's source control sidebar. Let me know how that works for you (here or at https://
58.
▲
by
sqs
2y ago
What would make it better than decent for you?
59.
▲
by
sqs
2y ago
Awesome to see our Rust fine-tune here on HN. We (Sourcegraph team) are here if anyone has questions or ideas for us! BTW, Cody is open source (Apache 2): https://github.com/sourcegraph/cody .
60.
▲
by
sqs
2y ago
Teams (that don't need Cody Enterprise) should just buy Cody Pro for each dev individually for now. We will have shared billing soon.
More ›