[aniforprez]

I understand the difference in UX but I'm really not concerned with that. The code itself is all open source for the VSCode client and will probably remain that way. Extensions like Pylance are replaceable and the Python extension can already just use Jedi instead. Also I'm sorry but that article is really terrible in terms of both content and layout. In terms of content, its only real argument is the .Net fiasco and some issue with Gitpod that really doesn't matter. In terms of content, the page is utterly unreadable

I'm perfectly aware of what Microsoft could do in some distant future. But as is, for all intents and purposes, VSCode is open source

[yjftsjthsd-h]

> But as is, for all intents and purposes, VSCode is open source

... Except that if you use the source to make your own build, you lose the extension ecosystem that is one of VSC's major selling points. It is at best a worked example of tivoization.

[aniforprez]

You can easily just download the extension dist files and dump it in the extensions folder. Most extensions are open source too and VScode is not doing anything special with the extension files. They're mostly just JS. You lose out on the convenience of the marketplace but the open source version exists. If a maintainer doesn't have their extension on there, usually reaching out to them will have them upload it there too or as I mentioned, just clone the repo

[torstenvl]

The extensions are compatible, aren't they?

    rm -fr ~/.vscode/*
    cp -a ~/.vscode-oss/* ~/.vscode/
    # Run VS Code, download extensions
    cp -a ~/.vscode/* ~/.vscode-oss/

Based on my recollection of migrating to VSCodium, all my extensions continued to work just fine.

I think there's also a hacky way to let VSCodium access the VS Code extension marketplace, but I believe it's an EULA violation.