by lobo_tuerto on 2/1/25, 5:31 PM with 30 comments
by itchynosedev on 2/4/25, 11:36 AM
However, it's baffling to me that by default Cline ignores `pkg/` folder that is common in Go projects. Check this issue - https://github.com/cline/cline/issues/927
I think Aider, Cline and Cursor are not far from each other in their capabilities.
Cursor was probably the most polished experience - especially their `Tab` autocomplete. However, I found this effect really interesting. Let's say 7 out of 10 times it's seamless, but there's uncanny valley of autocomplete in 3 out of 10 times - where you expect it to the right thing, but it either predicts wrong or takes a tad too long, 'breaking the immersion', if you will.
Cline does the job really well if you're in VSCode. Aider is great if you prefer terminal based workflow, or do not want to commit to another editor. Another great thing in Aider is `//AI!` comment. You can start Aider in --watch-files mode and it will watch for instructions, and start executing them. This way I can work in my preferred editor and have a tool in the background performing AI tasks.
A slight edge in my case goes to Aider for this reason, despite the fact that it does not feel quite as polished as the other two.
by trescenzi on 2/4/25, 1:31 PM
by pityJuke on 2/4/25, 1:24 PM
I do still find it the same 50/50 experience (maybe now closer to 65/45) as GH Copilot: sometimes whimsically amazing, sometimes horrifically confounding. And that’s not even with some of the complex code at work, that’s with some private, single file Python projects.
by d4rkp4ttern on 2/4/25, 1:03 PM
by byyoung3 on 2/4/25, 1:28 PM
by krystofee on 2/4/25, 12:37 PM
My problem with it is when its editing large files (1000+ LOC), because requests consume very many tokens AND it has problems editing the code so that sometimes its cycling infinitely trying to modify two lines in some function.
Anyway, I like it more then Cursor, because of the controll I have over the model and in some subjective ways its more pleasing to me seeing it "work".
by adamgordonbell on 2/4/25, 2:10 PM
It's great when it can self-check with tests and type-checking. Like 'upgrade this lib to the latest version and ensure everything is working after'.
Occasionally, it will go off target, get distracted by parse errors, rewrite some areas unnecessarily, and forget the original goal. It can end up yak shaving, and losing context of the task.
Agents also suck at global knowledge and will reimplement something that exists somewhere else, for instance. I have a rule: "Do information gathering first," which encourages it to look around a bit before making changes.
Seeing the context size like cline does is useful. I think the flow action credits in windsurf are a custom model for applying changes, and hence the separation.
by jacobpretorius on 2/4/25, 12:12 PM
by crestfallen33 on 2/4/25, 2:44 PM
by mrklol on 2/4/25, 2:00 PM
by barrenko on 2/4/25, 11:31 AM