danhab99@programming.dev to Programmer Humor@programming.dev · 2 年前emacsprogramming.devimagemessage-square80fedilinkarrow-up1640arrow-down179
arrow-up1561arrow-down1imageemacsprogramming.devdanhab99@programming.dev to Programmer Humor@programming.dev · 2 年前message-square80fedilink
minus-squareHurglet@lemmy.basedcount.comlinkfedilinkarrow-up3·2 年前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
minus-squaretostiman@sh.itjust.workslinkfedilinkarrow-up11·2 年前IIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binaries
minus-squareskarn@discuss.tchncs.delinkfedilinkarrow-up1·2 年前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.
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.