Cursor > Windsurf
Just trying it today and already closed it, it's constantly trying to change much more things that what I asked and also messed up the file codification so git thinks everything is new, also didn't make a good import from Cursor.
For me Cursor is working much better 🤷🏻♂️
I also found Windsurf defaults to "changing or creating" stuff, but a simple: "let's reason first, or don't create any files" solves it.
I didn't import anything settings from Cursor, so I don't know about that.
I still find Windsurf has better awareness of my codebase (Django, Redis, Postgres, Celery, all running via Docker for dev and prod).
Cursor is not good at understanding the setup.
I get your point.
My use case was different with lots of new files to generate and very little editing\changing.
I think that everything can be resolved with a better context.
I've seen people providing context.txt files for models to analyze and rely on during execution. Makes it easier to get what you want.
Cursor > Windsurf
Just trying it today and already closed it, it's constantly trying to change much more things that what I asked and also messed up the file codification so git thinks everything is new, also didn't make a good import from Cursor.
For me Cursor is working much better 🤷🏻♂️
I also found Windsurf defaults to "changing or creating" stuff, but a simple: "let's reason first, or don't create any files" solves it.
I didn't import anything settings from Cursor, so I don't know about that.
I still find Windsurf has better awareness of my codebase (Django, Redis, Postgres, Celery, all running via Docker for dev and prod).
Cursor is not good at understanding the setup.
I get your point.
My use case was different with lots of new files to generate and very little editing\changing.
I think that everything can be resolved with a better context.
I've seen people providing context.txt files for models to analyze and rely on during execution. Makes it easier to get what you want.