danhab99@programming.dev to Programmer Humor@programming.dev · 2 年前emacsprogramming.devimagemessage-square84linkfedilinkarrow-up1636arrow-down178
arrow-up1558arrow-down1imageemacsprogramming.devdanhab99@programming.dev to Programmer Humor@programming.dev · 2 年前message-square84linkfedilink
minus-squareEthab83@sh.itjust.workslinkfedilinkarrow-up18arrow-down2·2 年前It is, but the lack of official Microsoft extensions makes life a little harder
minus-squareHurglet@lemmy.basedcount.comlinkfedilinkarrow-up19·2 年前You can change the extension repository to the official one. I don’t need it tho, I only need Pyright, Python and the catppuccin theme
minus-squaretostiman@sh.itjust.workslinkfedilinkarrow-up5·2 年前Some MS addons still don’t work if you do that, last time I tried
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.
minus-squareskilltheamps@feddit.delinkfedilinkarrow-up3·2 年前The most unfortunate of which for me is remote development. So convenient, nothing compares :(
VSCodium > VSCode
It is, but the lack of official Microsoft extensions makes life a little harder
You can change the extension repository to the official one.
I don’t need it tho, I only need Pyright, Python and the catppuccin theme
Some MS addons still don’t work if you do that, last time I tried
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.
The most unfortunate of which for me is remote development. So convenient, nothing compares :(