zlacker

[return to "OpenAI reaches agreement to buy Windsurf for $3B"]
1. Androi+0W[view] [source] 2025-05-06 12:46:26
>>swyx+(OP)
Windsurf and Cursor feel like temporary stopgaps, products of a narrow window in time before the landscape shifts again.

Microsoft has clearly taken notice. They're already starting to lock down the upstream VSCode codebase, as seen with recent changes to the C/C++ extension [0]. It's not hard to imagine that future features like TypeScript 7.0 might be limited or even withheld from forks entirely. At the same time, Microsoft will likely replicate Windsurf and Cursor's features within a year. And deliver them with far greater stability and polish.

Both Windsurf and Cursor are riddled with bugs that don't exist upstream, _especially_ in their AI assistant features beyond the VSCode core. Context management which is supposed to be the core featured added is itself incredibly poorly implemented [1].

Ultimately, the future isn't about a smarter editor, it's about a smarter teammate. Tools like GitHub Copilot or future agents will handle entire engineering tickets: generating PRs with tests, taking feedback, and iterating like a real collaborator.

[0] https://www.theregister.com/2025/04/24/microsoft_vs_code_sub...

[1] https://www.reddit.com/r/cursor/comments/1kbt790/rules_in_49...

◧◩
2. leonid+g51[view] [source] 2025-05-06 13:44:30
>>Androi+0W
The thing is: we should not need standalone editors just to use AI coding agents. They could be just plugins, but Microsoft does not want to bend the plugin API enough for that. Windsurf has a "plugin edition" for JetBrains IDEs that works really, really well[0] (they also have a VSCode plugin[1] but it's lacking in comparison).

However, given that JetBrains also have their own AI offering[2], I'm not sure how long that will last too...

[0] https://plugins.jetbrains.com/plugin/20540-windsurf-plugin-f...

[1] https://marketplace.visualstudio.com/items?itemName=Codeium....

[2] https://www.jetbrains.com/ai/

◧◩◪
3. owenda+4d1[view] [source] 2025-05-06 14:26:41
>>leonid+g51
There are already a bunch of open source, free, and popular "AI coding agent" extensions for VS Code:

1) Cline (1.4mil downloads)

2) Roo Code (a fork of Cline, 450k downloads)

Still a drop in the bucket compared to Cursor in terms of # of users, but they're growing pretty fast.

Disclaimer: I maintain Kilo Code, which competes with 1) and 2) so I'm pretty familiar with this space/the growth patterns.

◧◩◪◨
4. htrp+wk1[view] [source] 2025-05-06 15:07:59
>>owenda+4d1
How are you differentiating from the cline/roo's of the world?
◧◩◪◨⬒
5. bolear+WH1[view] [source] 2025-05-06 17:15:25
>>htrp+wk1
Our plan is to be a superset of Cline and Roo's features (we already have all the major features from both) [0]

We also have our own provider, which means no need to bring your own API keys (you can if you like, but it is batteries included by default) and we're not charging anything on top of the API pricing. Instead of monetizing on individual developers, we want it to be free for them and make money eventually off enterprise contracts [1]

[0]: https://blog.kilocode.ai/p/roo-or-cline-were-building-a-supe... [1]: https://kilocode.ai

◧◩◪◨⬒⬓
6. UncleO+vC2[view] [source] 2025-05-07 00:11:45
>>bolear+WH1
maybe you could answer a question about kilo usage: If I choose Google Gemini as the API provider and give it my Gemini API key, why does it say that I'm low on credits (and I get API request failures immediately)? As far as I understand gemini 2.5 pro preview is free to use. (and in Cline I'm able to choose Google Gemini as the API provider & provide my API key and it will successfully make API requests)
◧◩◪◨⬒⬓⬔
7. hadesa+sK3[view] [source] 2025-05-07 13:19:34
>>UncleO+vC2
We added it to the issues: https://github.com/Kilo-Org/kilocode/issues/349
[go to top]