Using the C# debugger is also restricted to Visual Studio & VScode.
Microsoft loves open source, and windows is the most open operating system (look it up).
It’s totally not embrace, extend, extinguish in any disguise.
Coopetition exists (I’d point to the CNCF), but corporations do that really, really, begrudgingly only just due to the sheer complexity.
While I do not suspect that the somewhat benevolent notions will wane in the near future (the data is valuable enough, and you cannot afford to lose to another player), I sincerely enjoy just opting out because I like doing that.
Except, for example, VSCodium does not use vsdbg. It uses open-source NetCoreDbg maintained by Samsung and the fork of the extension, which itself is distributed under MIT and not subject to what article discusses.
But, you know, spreading FUD about .NET is way more important, is it not?
Not really a surprise. The TOS for the extension marketplace has been clear that it's only to be used for VS Code, that's why VSCodium doesn't use it. Cursor devs undoubtedly knew better, but kept breaking TOS and licenses, MS just chose a strategic moment to enforce the rules already in place.
Cursor not being an extension from the start seemed odd to me, and they wouldn't be in this rough spot if they had done that.
While also the TOS of their extensions like C/C++ also prohibit their usage with forks. It is not about using marketplace endpoint, it is about using the extension itself even if the user installed the vsix manually. At least this is what this submission about.
I would recommend getting started with lazyvim (lazyvim.org). Once you're comfortable with the editor, you can change the config to kickstart.nvim and start customizing it to your liking. That's what I did and I have no regrets. LazyVim allowed me to switch without sacrificing productivity. I was on it for a year before I decided to make my own config
No confirmation from MS, but as usual conspiracy theorists are confident in the final conclusion.
You'd think if the release of copilot's Agent mode is what prompted this move, they'd be doing it in those languages more popular among vibe-coders first wouldn't you?
Using the C# debugger is also restricted to Visual Studio & VScode. Microsoft loves open source, and windows is the most open operating system (look it up).
It’s totally not embrace, extend, extinguish in any disguise.
Coopetition exists (I’d point to the CNCF), but corporations do that really, really, begrudgingly only just due to the sheer complexity.
While I do not suspect that the somewhat benevolent notions will wane in the near future (the data is valuable enough, and you cannot afford to lose to another player), I sincerely enjoy just opting out because I like doing that.
Except, for example, VSCodium does not use vsdbg. It uses open-source NetCoreDbg maintained by Samsung and the fork of the extension, which itself is distributed under MIT and not subject to what article discusses.
But, you know, spreading FUD about .NET is way more important, is it not?
Must be a rough weekend for those working at cursor! Damn just when it’s starting to get really nice out too.
Seems like an unfair advantage in a market they control. Exercising monopolistic control
Not really a surprise. The TOS for the extension marketplace has been clear that it's only to be used for VS Code, that's why VSCodium doesn't use it. Cursor devs undoubtedly knew better, but kept breaking TOS and licenses, MS just chose a strategic moment to enforce the rules already in place.
Cursor not being an extension from the start seemed odd to me, and they wouldn't be in this rough spot if they had done that.
While also the TOS of their extensions like C/C++ also prohibit their usage with forks. It is not about using marketplace endpoint, it is about using the extension itself even if the user installed the vsix manually. At least this is what this submission about.
This is why I’m looking at neovim
As much as I like vscode it’s making me a little uncomfortable being reliant on it
But the configuration is a whole new project in lua. Saying I’ve being using neovim for a while, have shot myself in the foot a couple of times
I would recommend getting started with lazyvim (lazyvim.org). Once you're comfortable with the editor, you can change the config to kickstart.nvim and start customizing it to your liking. That's what I did and I have no regrets. LazyVim allowed me to switch without sacrificing productivity. I was on it for a year before I decided to make my own config
on Reddit: https://www.reddit.com/r/programming/comments/1jrl2zw/micros...
Embrace... Extend... Say it with me - EXTINGUISH!
Not really though, this seems like it was Cursors fault from the get go.
Perhaps. But I'm sure Microsoft releasing Agent mode at the same time is not a coincidence.
AMACM: awful microsoft anti-competition mechanism
No confirmation from MS, but as usual conspiracy theorists are confident in the final conclusion.
You'd think if the release of copilot's Agent mode is what prompted this move, they'd be doing it in those languages more popular among vibe-coders first wouldn't you?