99
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Jan 2024
99 points (95.4% liked)
Unixporn
15465 readers
9 users here now
Unixporn
Submit screenshots of all your *NIX desktops, themes, and nifty configurations, or submit anything else that will make themers happy. Maybe a server running on an Amiga, or a Thinkpad signed by Bjarne Stroustrup? Show the world how pretty your computer can be!
Rules
- Post On-Topic
- No Defaults
- Busy Screenshots
- Use High-Quality Images
- Include a Details Comment
- No NSFW
- No Racism or use of racist terms
founded 5 years ago
MODERATORS
Well, as a non-native I may have used the wrong word. I meant: I care about getting things done quickly, without some extension not working or behaving weirdly because I built it in the slightest wrong way due to some unknown bug or problem. I love and prefer to tinker with all of my software stack except vscode: I tried VSCodium once and I don't know why, but many of the plugins I needed didn't work properly. Surely it is my fault, but I am not in a position to invest time in such a fundamental working tool (at least for me).
On a note: I even had problems with Cursor, the AI-powered fork of VSCodium. Looks like VSCode is helding me hostage
It's the exact same setup as code, if the extensions work in VSCode they work in Sodium except a select few Microsoft created.
Any extension that you cannot install directly from Codium, you can just manually download/install the VSIX file for from GitHub or whatever.
https://github.com/VSCodium/vscodium/blob/master/docs/index.md#extensions-marketplace
Even copilot etc? I thought there was an issue with installing certain GitHub/Microsoft extensions.