Cline is a great alternative to Cursor if you are not willing to switch over to another (forked) editor.
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.
Tangential but “AI Engineering” to me implies working on AI not with AI. The article has some solid examples of how this tool is helpful but if we’re going to start to call all software development done with LLM assistance AI Engineering, “AI” and “Engineering” are going to lose all meaning even faster than they currently are.
Cline/Roo & Aider with Claude 3.5 are certainly at the better end of AI programming assistance from my (limited!) experience.
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.
"Cline approaches AI assistance differently from most tools in the market" - I'm not trying to be a hater but I feel like it isn't that much different from cursor?
itchynosedev ·12 days ago
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.
Show replies
trescenzi ·12 days ago
Show replies
pityJuke ·12 days ago
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.
Show replies
d4rkp4ttern ·12 days ago
Show replies
byyoung3 ·12 days ago
Show replies