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...
The last cycle I remember of this IMO is iPython -> Jupyterhub/Jupyterlab. Of course, iPython has existed for a long time, though that change was made because data was too big to analyze locally and it turns out it was more convenient to centrally manage kernels/images/libraries for convenience.
MCP servers and Cursor/Windsurf changed that a bit, but it will end up centralized again at some point (or at least aggregated, if it's not already?). People are passing around lists of interesting MCP servers now, and that will be out of fashion in less than 12 months.