←back to thread

316 points skarat | 1 comments | | HN request time: 0.203s | source

Things are changing so fast with these vscode forks I m barely able to keep up. Which one are you guys using currently? How does the autocomplete etc, compare between the two?
Show context
joelthelion ◴[] No.43959984[source]
Aider! Use the editor of your choice and leave your coding assistant separate. Plus, it's open source and will stay like this, so no risk to see it suddenly become expensive or dissappear.
replies(4): >>43960110 #>>43960122 #>>43960453 #>>43961416 #
mbanerjeepalmer ◴[] No.43960110[source]
I used to be religiously pro-Aider. But after a while those little frictions flicking backwards and forwards between the terminal and VS Code, and adding and dropping from the context myself, have worn down my appetite to use it. The `--watch` mode is a neat solution but harms performance. The LLM gets distracted by deleting its own comment.

Roo is less solid but better-integrated.

Hopefully I'll switch back soon.

replies(1): >>43960199 #
fragmede ◴[] No.43960199[source]
I suspect that if you're a vim user those friction points are a bit different. For me, Aider's git auto commit and /undo command are what sells it for me at this current junction of technology. OpenHands looks promising, though rather complex.
replies(1): >>43960384 #
movq ◴[] No.43960384[source]
The (relative) simplicity is what sells aider for me (it also helps that I use neovim in tmux).

It was easy to figure out exactly what it's sending to the LLM, and I like that it does one thing at a time. I want to babysit my LLMs and those "agentic" tools that go off and do dozens of things in a loop make me feel out of control.

replies(2): >>43960675 #>>44022287 #
1. charlie0 ◴[] No.44022287[source]
I like to be the human in the loop and everytime it does something I don't like, I will add a rule in conventions.md. Overtime, I watch it less and less.