zlacker

>>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...

>>Androi+0W
Copilot owns the platform, had an amazing head start and yet still is the worst option available. I don’t mean to be harsh but this was a titanic fumble.

>>bn-l+w01
GitHub has been failing upward for more than 5 years. They could have totally dominated software development and security - failed. Could have been the undisputed champion of code hosting - failed. Should have dominated development co-pilots - failed.

I actually find it a little reassuring that they can't seem to get out of their own way.

>>bearde+v21
To be fair, they have been behind the competition for many years. Gitlab had extremely good CI, security scanning, organisational concepts, etc. for years before GitHub introduced their ones (and Actions still has a worse UX, and GitHub still doesn't have anything below an organisation).

>>sofixa+G91
Well you’re right (especially wrt things like security scanning), but you sort of have to include Azure DevOps in the conversation nowadays. I think the end goal for Microsoft is to get the larger organizations into ADO, either cross-pollinate pipelines and actions or just replace actions with pipelines at some point, and leave GitHub for simpler project structures and public codebases.

That’s why you won’t see a ton of work go into e.g. issues/projects on GitHub. Those features all already exist and are very robust in ADO, so if you need those kinds of things (and the reporting an enterprise would want to be able to run on that data), then you belong on ADO.

>>twodav+lP1
I can say with a high level of confidence that the goal is definitely not to push larger orgs to ADO over GitHub. ADO is and will continue to be supported and you’re right that its project management features are much more advanced than GitHub, but the mission is not to push people off of ADO and into GitHub.