[zeusflight]

How about the fact that some extensions like Remote Development [1] and LiveShare [2] work only on proprietary builds of vscode, and not on code-oss or vscodium? I get it that those are proprietary extensions, but they still show up in the extension marketplace for OSS builds. And I don't see a technical reason why they wont run on OSS builds, other than that the extension builders want it that way. And these extensions are important enough that you will end up downloading the proprietary build while you are too busy solving something with your team mates. This is a very subtle way to push even privacy-aware developers to use the proprietary build with built-in telemetry.

And how about the fact that the de-facto reference implementation of LSP client (most language servers are developed against vscode) uses many undocumented and non-standard extensions [3] that are hard for other clients to implement?

These are dark patterns that claims to be FOSS-friendly. It could be that MS still has split-brains about their approach to open source [4], but that is still an indication that MS still has part of their old anti-user soul in them. Personally, I liked vscode, but I value my freedom even more. Emacs provides all the functionality and the freedom I crave. It is a bit harder to learn and modify - but I can live with that.

[1] https://github.com/VSCodium/vscodium/issues/240#issuecomment...

[2] https://github.com/VSCodium/vscodium/issues/128#issuecomment...

[3] https://github.com/microsoft/python-language-server/issues/4...

[4] https://www.theverge.com/2021/10/22/22740701/microsoft-dotne...

[coldacid]

Good response, thanks.