3 ms·

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

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

Pannoniae 2y ago
They have integrity checks and obfuscated code. That's not just changing a few settings. See the issue I linked about Pylance, for example...
throwup238 2y ago
> It's just not officially supported. 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.
- wkat4242 2y ago
  Meh, for me personally I don't care about EULAs, as you say. 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.
  - wiseowise 2y ago
    > And for business, they will use the official VS Code anyway. Our company only has VSCodium in their repos.
slimsag 2y ago
Its close in spirit to DRM: they enforce that if you are using their projects, it is under their legal terms. 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#issuecomment-719063505 https://github.com/microsoft/vscode-cpptools/issues/6388#iss... [1] https://github.com/microsoft/vscode-cpptools/issues/5784 https://github.com/microsoft/vscode-cpptools/issues/5784 [2] https://github.com/microsoft/win32metadata/issues/766 https://github.com/microsoft/win32metadata/issues/766 [3] https://devlog.hexops.com/2024/building-the-directx-shader-compiler-better-than-microsoft/#introducing-dxildll---the-proprietary-code-signing-blob-for-directx-shaders https://devlog.hexops.com/2024/building-the-directx-shader-c... [4] https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/1521 https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/...
Hackbraten 2y ago
The Pylance extension literally attacks your computer using a ReDoS attack if you open it in a debugger. [0] [0]: https://darmstadt.social/@claudi/112866065489514979 https://darmstadt.social/@claudi/112866065489514979

Pannoniae 2y ago

They have integrity checks and obfuscated code. That's not just changing a few settings. See the issue I linked about Pylance, for example...

throwup238 2y ago

> It's just not officially supported. 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.

wkat4242 2y ago
Meh, for me personally I don't care about EULAs, as you say. 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.
- wiseowise 2y ago
  > And for business, they will use the official VS Code anyway. Our company only has VSCodium in their repos.

slimsag 2y ago

Its close in spirit to DRM: they enforce that if you are using their projects, it is under their legal terms. 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#issuecomment-719063505 https://github.com/microsoft/vscode-cpptools/issues/6388#iss... [1] https://github.com/microsoft/vscode-cpptools/issues/5784 https://github.com/microsoft/vscode-cpptools/issues/5784 [2] https://github.com/microsoft/win32metadata/issues/766 https://github.com/microsoft/win32metadata/issues/766 [3] https://devlog.hexops.com/2024/building-the-directx-shader-compiler-better-than-microsoft/#introducing-dxildll---the-proprietary-code-signing-blob-for-directx-shaders https://devlog.hexops.com/2024/building-the-directx-shader-c... [4] https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/1521 https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/...

Hackbraten 2y ago

The Pylance extension literally attacks your computer using a ReDoS attack if you open it in a debugger. [0] [0]: https://darmstadt.social/@claudi/112866065489514979 https://darmstadt.social/@claudi/112866065489514979