Why is there a waiting list if it's open source?
Show HN: Void, an open-source Cursor/GitHub Copilot alternative
101–110 of 168 posts
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#102Good job at creating more competition, but sorry for being a little bit rude, most software forks die out, try to convince me using this instead of Continue + Claude-dev, which are open source extensions for the vanilla VSCode (or VSCodium). >Microsoft also made its extension marketplace closed-source Ehm, Open VSX Registry exists.
Are you using a local model with Continue?
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#103I think more competition in the "AI Editor" space is good, but I have to ask – why not make it a VSCode extension? I feel it'd be much more accessible. Are there limitations in the extension APIs that make it hard to implement?
Agreed, it’s not perfect but VS code is a pretty rich ecosystem. Dealing with the drift between a fork and the core product — and missing features/broken extensions that’ll inevitably come with that isn’t really something I want to deal with in my work flow.
Cursor has a pretty polished experience, but I keep coming back to VS Code and using continue.dev, which is a lot rougher around the edges, because the UI works well enough.
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#104I’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).
Is there a technical limitation of the extension APIs or is it easier to “market” a new editor than an editor extension?
While adoption for individuals and small companies might be easy, a lot of bigger places already have other integrations with existing IDEs and displacing those for yet another IDE will be a hard ask
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#105> All of the code is OOP-based, and they mount DOM nodes the old-school way (which is what React was supposed to solve..)
I don't know about VS Code, but I remember Atom was refactored to use manual DOM updates because the performance penalty of using React wasn't worth it.[1] By the way, isn't OOP by far the most popular paradigm for building desktop UIs? I imagine VS Code is a difficult codebase to work with that has a lot of intricate code (as is usually the case with large software projects), but that's a strange piece of criticism :-)
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#106So early stage that we can't download it? Why would I want to join a discord server for a code editor? What is the plan when VS Code introduces all your features?
Well the code is there: https://github.com/voideditor/void/tree/main/extensions/void
But it's super basic right now... Like literally just the bare minimum to make an LLM call in a side window and a view to apply/reject diffs. Pretty much a weekend project at this point.
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#107So early stage that we can't download it? Why would I want to join a discord server for a code editor? What is the plan when VS Code introduces all your features?
Maybe that's the point. Who is going to be acquired by Microsoft and then just be part of VS Code?
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#108Good job at creating more competition, but sorry for being a little bit rude, most software forks die out, try to convince me using this instead of Continue + Claude-dev, which are open source extensions for the vanilla VSCode (or VSCodium). >Microsoft also made its extension marketplace closed-source Ehm, Open VSX Registry exists.
Are you using a local model with Continue?
I've tried running 3B LLAMA on my old machine and it was sluggish and kinda bad, but Claude 3.5 Sonnet works great. I will try the 70B model, should be good enough.
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#109I’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). Is there a technical limitation of the extension APIs or is it easier to “market” a new editor than an editor extension? While adoption for individuals and small companies might be easy, a lot of bigger places already have other integration…
Extracting from cursor team [1]
> VSCode extensions have very limited control over the UI of the editor. Our Command-K and Copilot++ features aren’t possible as extensions. Same for much of what we want to build in the future!
Re: Show HN: Void, an open-source Cursor/GitHub Copilot alternative
#110This investment by YC in both Void and Continue.dev perfectly exemplifies the VC spray-and-pray approach by backing two nearly identical open-source VSCode plugins for AI-assisted coding. They're simply throwing money at similar projects in the same space, hoping one will stick, without any special insight or reason why one should be more successful over another.
This is VC operations by design since forever.
Heck, even centuries ago, they'd fund multiple ship crews to navigate the Earth, hoping one would find smth interesting.
It's the model that works in high-risk, high-reward endeavors.