News for hackers. Stuff that matters.

A comment on Microsoft blocks VSCode-derived editors (like Cursor) from using MS extensions. Parent comment

Re:Microsoft blocks VSCode-derived editors (like Cursor) fro... by flohofwoe on Saturday April 05, 2025 @04:47AM (#43591964)
This is about closed-source extensions created by Microsoft, and those always had strings attached which Cursor apparently ignored.

I would rather ask Cursor why they decided to fork VSCode when they could simply have written yet another VSCode extension to provide the same functionality. Seems shady AF tbh.

[ Parent | on HN ]
Re:Microsoft blocks VSCode-derived editors (like Cursor) fro... by bn-l on Saturday April 05, 2025 @10:46AM (#43593911)
Doesn’t Microsoft handicap extensions by not giving them the full access that co-pilot gets? You’d be crazy to compete when the other side literally owns the platform.
[ Parent | on HN ]
Re:Microsoft blocks VSCode-derived editors (like Cursor) fro... by gkbrk on Sunday April 06, 2025 @08:30AM (#43600974)
Why is it shady to fork an open-source project? If they didn't want forks they should have released it under a non-open-source license.
[ Parent | on HN ]
Re:Microsoft blocks VSCode-derived editors (like Cursor) fro... by siva7 on Sunday April 06, 2025 @12:20PM (#43602619)
They couldn't have done and it gets tiresome to repeat the technical limitations on extensions for vscode again and again (which don't apply to Microsoft owned extensions like Github Copilot) when you can google it yourself.
[ Parent | on HN ]
Re:Microsoft blocks VSCode-derived editors (like Cursor) fro... by behnamoh on Sunday April 06, 2025 @10:53PM (#43607142)
Continue and several other extensions do what Cursor does and they're extensions. No excuses from Cursor are acceptable.
[ Parent | on HN ]