6 ms·
I've played with Cursor, it felt like all it has is a simple wrapper around Claude. It repeats what I've been doing manually before, namely copy pasting small c
by a_bonobo 2y ago
I've played with Cursor, it felt like all it has is a simple wrapper around Claude. It repeats what I've been doing manually before, namely copy pasting small code blocks into Claude and asking it to fix it. Cursor doesn't add much to that, plus it struggles sometimes when Claude says to insert something somewhere, Cursor fails to find out where that 'somewhere' is. The 'edit in text' function feels identical to Github Copilot, perhaps better in immeasurable 'quality' since Claude codes pretty well.
Somewhere out there is a far more 'native' way of coding with the AI together, where the LLM constantly sees the entire code base as you code; you don't code 'into the codebase', but you code 'into the LLM'. Hard to explain what I mean here...
- Joaomcabrita 2y agoYou could vectorize the whole codebase and then keep having a conversation about it, update files in the vector, and so on. The problem is if the LLM actually understands nuances and dependencies in the codebase structure. For some languages and clear frameworks maybe so, but in many cases it could still misinterpret. Doable though imho to improve it.