It's not really DRM. You can make most extensions work on codium by changing a few settings. It's just not officially supported.
I hate the way they don't open source the useful ones like the ssh debugging though
I hate the way they don't open source the useful ones like the ssh debugging though
Many of their VS Code extensions[0] have license terms which /prohibit/ them from being used in editors that are not Microsoft's VS Code editor, and Microsoft can issue cease-and-desist for violations of this, as well as 'open source forks of VS Code' using their marketplace services.
Microsoft also has a pattern they follow where they publish repositories on GitHub to proclaim they are open source, while actually distributing proprietary binary blobs in them that are fundamental core parts of functionality to the codebase[2][3][4]
[0] https://github.com/microsoft/vscode-cpptools/issues/6388#iss...
[1] https://github.com/microsoft/vscode-cpptools/issues/5784
[2] https://github.com/microsoft/win32metadata/issues/766
[3] https://devlog.hexops.com/2024/building-the-directx-shader-c...
[4] https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/...
Isn't it worse than that? They're not just unsupported, I thought it was against their EULA to use the MS extensions with anything but the official VSCode.
It doesn't matter to the average person using it for personal projects but it's a liability to businesses. It wouldn't matter most of the time but this is Microsoft we're talking about.
And for business, they will use the official VS Code anyway. My own employer is up to their armpits in Satya's ass. Over the last 8 years the MS sales goons have managed to get us to throw out every third party solution they had an option for. We even have to use Edge now.
Our company only has VSCodium in their repos.