andrewpareles

4 ms·

1.
by andrewpareles 1y ago
I think a good use of time while waiting for an LLM is to ask another LLM for something. Until then Slack will do :)
2.
by andrewpareles 1y ago
This is completely true, and it's a really common objection. I don't imagine people will want to fully visualize codebases in a giant unified diagram, but I find it hard to imagine that we won't have digests and overviews tha
3.
by andrewpareles 1y ago
I should have been more careful with my wording - I was talking about major VS Code-based IDEs as alternatives. Zed is very impressive, and we've been following them since before Void's launch!
4.
by andrewpareles 1y ago
Thanks for writing! Can you try mentioning the file with "@"? Smaller models sometimes don't realize that they should look for files and folders, but "@" always gives the full context of whatever is in the file&#x2F
5.
by andrewpareles 1y ago
Just want to share our thinking on terminal-based tools! We think in 1-2 years people will write code at a systems level, not a function level, and it's not clear to us that you can do that with text. Text-based tools like Claude Code
6.
by andrewpareles 1y ago
Yep, Void is a VSCode fork, but we're definitely not wed to VSCode! Building our own IDE/browser-port is not out of the picture. We'll have to see where the next iteration of tool-use agents takes us, but we strongly feel wri
7.
by andrewpareles 1y ago
We considered Theia, and even building our own IDE, but obviously VSCode is just the most popular. Theia might be a good play if Microsoft gets more aggressive about VSCode forks, although it's not clear to us that people will be spen
8.
by andrewpareles 1y ago
Agreed - this is one of the better solutions today.
9.
by andrewpareles 1y ago
This is a good point.We've stayed away from documentation assuming that it's more of a browser agent task, and I agree with other commenters that this would make a good MCP integration. I wonder if the next round of models trained
10.
by andrewpareles 1y ago
Thanks for the feedback. We'll definitely add a feature list. To answer your question, yes - we support Cursor's features (quick edits, agent mode, chat, inline edits, links to files/folders, fast apply, etc) using open sourc
11.
by andrewpareles 1y ago
Interesting, thanks for sharing! We planned on spinning up a new Git branch and shallow Git clone (or possibly worktree/something more optimized) for each agent, and also adding a small auto-merge-with-LLM flow, although something more
12.
by andrewpareles 1y ago
We think terminal tools like Claude Code are a good way for research teams to experiment with tool use (obviously pure text), but definitely don't see the terminal as the endgame for these tools. I know some folks like using the termin
13.
by andrewpareles 1y ago
Continue is doing great work, but they're an extension (plugin)!
14.
by andrewpareles 1y ago
Yes, you can bring OpenRouter or any other provider and connect directly! (We don't route your messages through a backend like others).
15.
by andrewpareles 1y ago
Void dev here! The biggest players in AI code today are full IDEs, not just extensions, and we think that's because they simply feel better to use by having more control over the UX. There are certainly a lot of alternatives that are p
16.
by andrewpareles 1y ago
Void dev here! As others have mentioned, VSCode strongly limits the functionality that you can build as an extension. A few things we've built that aren't supported as an extension: - the Accept|Reject UI and UX - Cmd+K - Control
17.
by andrewpareles 2y ago
> I’d love a good summary on why Cursor, Void (and I assume other tools) decided to build new editors instead of just extending the incumbents (VSCode extension, Jetbrains plugins). This is a great question. We think extensions are often
18.
by andrewpareles 2y ago
Hey, great question - you're right, extensions are more accessible - the thing is, there is no great way to build the native UI we'd want using them. For example, displaying the before-and-after is vital for us, and doesn't f
19.
by andrewpareles 2y ago
Thanks for sharing! If Theia is built on top of monaco, I wonder if a form of one-click switch might work. The monaco editor is theoretically part of the vscode repo, while the "workbench" with settings/configs lives one laye
20.
Show HN: Void, an open-source Cursor/GitHub Copilot alternative(github.com)
347 points by andrewpareles 2y ago|154 comments
21.
by andrewpareles 2y ago
Pear consists largely of a VS Code extension built on top of Continue.dev's VS Code extension. We're building a more native integration into the VS Code editor, similar to Cursor. Is there anything you like about Pear that Cursor
22.
by andrewpareles 2y ago
Great question - we're doing a VS Code clone to have access to features like language servers, debugging, extensions, etc - these are really annoying to build from scratch. We also think it's nice for users to just be able to do a
23.
by andrewpareles 2y ago
We really like about on-prem models as well - it definitely seems they will get comparable and win over paying for API credits. Will make the first batch of releases ASAP!
24.
Show HN: Void - open source Cursor AI code editor(voideditor.com)
13 points by andrewpareles 2y ago|8 comments
25.
Show HN: an AI copilot for Next.js developers(useglass.ai)
13 points by andrewpareles 2y ago|2 comments