Coding Spark is on Again

I installed a new IDE yesterday. It is a Cursor competitor called Windsurf, which is yet another fork from VSCode.

I decided to give it a go, even after being in love with Cursor because after seeing a Youtube video about it, I saw it had something I have been missing when using Cursor, and that is content awareness.

I didn’t know what to expect really, because after all, I was watching someone else try it on their machine with a simple made up codebase, but I decided to cancel my Cursor subscription (I haven’t coded and used Cursor for 2 months now, while continuing to pay the 20$/month subscription).

By the way, after cancelling Cursor, I got an auto-reply from one of the founders asking for feedback. The email was so well written (though I knew it was an automation) that I decided to reply. They automatically gave me a refund for the last month! I’ll definitely come back to Cursor at some point.

Installing Windsurf went without any hiccups. I found out I have a pro-trial for 7 days, so I decided to put it to a test of fire while I was at it. I opened my jobsinenglish.dk codebase and asked it for a task I had been putting off for a while.

Wow. It performed almost flawlessly, but what I liked the most in their implementation of Cursor’s composer, which they call Cascade, is that it actually searches relevant stuff in the codebase and acts accordingly, it reasons with itself and you can see that.

In contrast, you could @codebase in Cursor and never get this level of awareness and understanding of the codebase.

All in all, I will keep on testing Windsurf, and report back.