Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
1–10 of 37 posts
Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#2Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#3I was coding with VSCode for a while and just this week decided to try Cursor which everyone have been raving about. Was quite disappointed to find no meaningful difference with VSCode (so far, after 30 minutes of working with it).
Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#4I was coding with VSCode for a while and just this week decided to try Cursor which everyone have been raving about. Was quite disappointed to find no meaningful difference with VSCode (so far, after 30 minutes of working with it).
Maybe Cursor/Windsurf could've just been plugins? Only Zed.ai seems really different of the popular IDEs
Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#5I was coding with VSCode for a while and just this week decided to try Cursor which everyone have been raving about. Was quite disappointed to find no meaningful difference with VSCode (so far, after 30 minutes of working with it).
It's a fork of VS Code that still uses the official extensions, despite that violating the license terms. Functionally, it's pretty similar to using VS Code with Copilot, but with the added bonus of choosing from multiple models. I’ve only just started using it at work, so my experience is also pretty limited, but so far the results seem slightly better.
Isn't the situation similar to Brave et al built on top of Chromium but supports Chrome extensions?
Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#6I was coding with VSCode for a while and just this week decided to try Cursor which everyone have been raving about. Was quite disappointed to find no meaningful difference with VSCode (so far, after 30 minutes of working with it).
It's a fork of VS Code that still uses the official extensions, despite that violating the license terms. Functionally, it's pretty similar to using VS Code with Copilot, but with the added bonus of choosing from multiple models. I’ve only just started using it at work, so my experience is also pretty limited, but so far the results seem slightly better.
Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#7I was coding with VSCode for a while and just this week decided to try Cursor which everyone have been raving about. Was quite disappointed to find no meaningful difference with VSCode (so far, after 30 minutes of working with it).
It's a fork of VS Code that still uses the official extensions, despite that violating the license terms. Functionally, it's pretty similar to using VS Code with Copilot, but with the added bonus of choosing from multiple models. I’ve only just started using it at work, so my experience is also pretty limited, but so far the results seem slightly better.
On the other hand, I think MS are pretty much cloning the good stuff from Cursor, like agent mode: https://www.youtube.com/watch?v=dutyOc_cAEU
Leaves me thinking VS Code might be the best in the long long run, but for now they're all kinda similar?
Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#8Earlier quoted context omitted.
It's a fork of VS Code that still uses the official extensions, despite that violating the license terms. Functionally, it's pretty similar to using VS Code with Copilot, but with the added bonus of choosing from multiple models. I’ve only just started using it at work, so my experience is also pretty limited, but so far the results seem slightly better.
How is it violating license terms? As far I know, vscode is released under a permissive open source license. Isn't the situation similar to Brave et al built on top of Chromium but supports Chrome extensions?
Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#9Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)
#10For example, the mentioned graph has "initial prompt with iterative tweaks", followed by iterations of 'starting from scratch'. -- I don't understand why you'd think "this is an ineffective way of doing things", and then keep doing it.
Describing LLMs as "slot machines" seems like the author has no curiosity about the shape of what LLMs can/can't do.