3 ms·

> "destroying a lot of the IDE/editor ecosystem" How is Microsoft releasing VS Code "destroying the editor ecosystem" but releasing Vim for free isn't and JetB

> "destroying a lot of the IDE/editor ecosystem" How is Microsoft releasing VS Code "destroying the editor ecosystem" but releasing Vim for free isn't and JetBrains charging for their IDEs isn't? This isn't "EEE" this is whining that Microsoft is competing by making software people want and that's unfair, apparently. > "just to eventually remove the important bits into non-free plugins, making the free version of codium basically pointless." Look at what isn't open source: https://github.com/microsoft/vscode/wiki/Differences-between-the-repository-and-Visual-Studio-Code https://github.com/microsoft/vscode/wiki/Differences-between... Microsoft logos and trademarks, integration with a marketplace which Microsoft run, a list of extensions Microsoft have reviewed and recommend (not the extensions, just the list), just enough of the Remote Development feature to handle connecting to Microsoft's backend for it, Telemetry, and autoupdate from Microsoft servers. Arguing those are "the important bits" is a stretch. The C#/.NET debugger maybe, but you say that was "eventually removed into non-free plugin" - was it ever free? It doesn't sound like it. Also VS Code was popularised by JavaScript and TypeScript not C#, that's always been the province of Visual Studio full edition.

411111111111111 4y ago
I consider the MS Language Servers pretty much the most important bit of vscodes IDE functionality as it provides autocompletion, lookup, refactoring etc, which is the feature i was specifically thinking of here. They were originally all open source, but aren't anymore. they're still free (as in beer), but their licence only allows usage with the official visual studio code distribution
- delta_p_delta_x 4y ago
  The thing is that those extensions are Microsoft's, and as problematic as some people consider the situation to be, Microsoft has all the right to limit the licence for these extensions. The inconvenient answer: want another C# extension? Tough luck, write it yourself. This is essentially what LLVM did for C/C++ linting, and produced Clangd, and many people now consider it to be superior to the Microsoft C/C++ linter.
  - KyeRussell 4y ago
    Nobody is arguing that they don’t have the right to. This is such an American argument of last resort I have no idea how we always end up here. I’m not nearly as anti-modern-Microsoft as some of the people here, but even I know that “they have the right to” is moving the goalposts.
  - mycall 4y ago
    Mono C# used LLVM but Microsoft thought their language services were better, so mono LLVM is EOL.

411111111111111 4y ago

I consider the MS Language Servers pretty much the most important bit of vscodes IDE functionality as it provides autocompletion, lookup, refactoring etc, which is the feature i was specifically thinking of here. They were originally all open source, but aren't anymore. they're still free (as in beer), but their licence only allows usage with the official visual studio code distribution

delta_p_delta_x 4y ago
The thing is that those extensions are Microsoft's, and as problematic as some people consider the situation to be, Microsoft has all the right to limit the licence for these extensions. The inconvenient answer: want another C# extension? Tough luck, write it yourself. This is essentially what LLVM did for C/C++ linting, and produced Clangd, and many people now consider it to be superior to the Microsoft C/C++ linter.
- KyeRussell 4y ago
  Nobody is arguing that they don’t have the right to. This is such an American argument of last resort I have no idea how we always end up here. I’m not nearly as anti-modern-Microsoft as some of the people here, but even I know that “they have the right to” is moving the goalposts.
- mycall 4y ago
  Mono C# used LLVM but Microsoft thought their language services were better, so mono LLVM is EOL.