emacsdanhab99@programming.dev to Programmer Humor@programming.dev – 561 points – 9 months ago81Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentSome MS addons still don't work if you do that, last time I triedThe most unfortunate of which for me is remote development. So convenient, nothing compares :(That's weird, AFAIk VSCodium only strips telemetry and changes branding. It shouldn't actively break addon. Unless they check if they're running inside of the actual MS VSCode, which could explain why they aren't workingIIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binariesYou can get e.g. pylance to work if you trick it: https://github.com/VSCodium/vscodium/issues/1640 So, at least in that instance, it's just Microsoft being a little petty.
Some MS addons still don't work if you do that, last time I triedThe most unfortunate of which for me is remote development. So convenient, nothing compares :(That's weird, AFAIk VSCodium only strips telemetry and changes branding. It shouldn't actively break addon. Unless they check if they're running inside of the actual MS VSCode, which could explain why they aren't workingIIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binariesYou can get e.g. pylance to work if you trick it: https://github.com/VSCodium/vscodium/issues/1640 So, at least in that instance, it's just Microsoft being a little petty.
That's weird, AFAIk VSCodium only strips telemetry and changes branding. It shouldn't actively break addon. Unless they check if they're running inside of the actual MS VSCode, which could explain why they aren't workingIIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binariesYou can get e.g. pylance to work if you trick it: https://github.com/VSCodium/vscodium/issues/1640 So, at least in that instance, it's just Microsoft being a little petty.
IIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binariesYou can get e.g. pylance to work if you trick it: https://github.com/VSCodium/vscodium/issues/1640 So, at least in that instance, it's just Microsoft being a little petty.
You can get e.g. pylance to work if you trick it: https://github.com/VSCodium/vscodium/issues/1640 So, at least in that instance, it's just Microsoft being a little petty.
Some MS addons still don't work if you do that, last time I tried
The most unfortunate of which for me is remote development. So convenient, nothing compares :(
That's weird, AFAIk VSCodium only strips telemetry and changes branding. It shouldn't actively break addon.
Unless they check if they're running inside of the actual MS VSCode, which could explain why they aren't working
IIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binaries
You can get e.g. pylance to work if you trick it:
https://github.com/VSCodium/vscodium/issues/1640
So, at least in that instance, it's just Microsoft being a little petty.