@danhab99@programming.dev to Programmer Humor@programming.dev • 1 year agoemacsprogramming.devimagemessage-square88fedilinkarrow-up1640arrow-down179
arrow-up1561arrow-down1imageemacsprogramming.dev@danhab99@programming.dev to Programmer Humor@programming.dev • 1 year agomessage-square88fedilink
minus-squareHurgletlinkfedilink3•1 year agoThat’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-square@tostiman@sh.itjust.workslinkfedilink11•1 year agoIIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binaries
minus-square@skarn@discuss.tchncs.delinkfedilink1•1 year agoYou 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.