141–150 of 168 posts
there is also PearAI - "The Open Source AI-Powered Code Editor. A fork of VSCode and Continue." [0]. It's getting very crowded in this space: cursor.sh, continue.dev, double.bot, supermaven, codium.ai, PearAI and now Void. [0] - https://github.com/trypear/pearai-app
Seems to be a dupe of another Show HN post posted by the same user 4 days ago https://news.ycombinator.com/item?id=41523197
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). 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…
Someone else mentioned monetization, which may be the real reason.
Cursor needs some competition. Their generation quality fell off a cliff recently as they are doing behind the scenes product optimizations with LLMs
there is also PearAI - "The Open Source AI-Powered Code Editor. A fork of VSCode and Continue." [0]. It's getting very crowded in this space: cursor.sh, continue.dev, double.bot, supermaven, codium.ai, PearAI and now Void. [0] - https://github.com/trypear/pearai-app
If you've tried others, would love to understand if there's anything you didn't like specifically (I'm one of the creators for https://double.bot )
I would recommend update double.bot landing page to have all features shown in few gifs on the same page and 'show in action' short video' - continue.dev had actually pretty good landing page. CodeSnap is probably something similar like cursors' 'apply' but double.bot landing page feels more like documentation. Also at this stage probably worth to add additional comparison to cursor same like you have for copilot
As someone who has recently tried to refactor our app atop of VSCode (treating it like a platform), we got burned by the UI design decisions that are not straightforward to overcome, let alone maintain. The closed-source MS marketplace did not help either towards our OSS goals. However, I found Theia ( https://theia-ide.org ) on HN (like a bunch of other cool things; this is one way I justify the time I spend/sink on…
This 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.
I 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?
Extensions like Codeium do the most naive thing possible by writing something like >>>>>>> in your file, literally breaking syntax highlighting. Others like Copilot are super buggy.
Right now Void is built on top of an extension, but we're also modifying and hooking into parts of the IDE to make a more native UX.
Earlier quoted context omitted.
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! [1] https://forum.cursor.com/t/why-not-a-plugin/2448/2
I don't fancy a future of multiple diverging VSCode forks. I wonder if they could have created a "Super Plugin" interface instead of a Cursor specific fork and try to get it merged to VSCode or VSCodium or at least keep as a new shared platform for deep customisation instead of balkanisation by everyone interested in doing something similar.
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). 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…