Honestly, I love Microslop's #VSCode #editor.
-
Honestly, I love Microslop's #VSCode #editor. I could do with a little less telemetry and AI bullshit though, so I'm keeping an eye on https://vscodium.com/ - I tried it briefly, but it wasn't simply plug and play, so I'm trying to gather the willpower to give it another go.
As I recall, one of the major issues for me was the absence of reliable configuration synchronization between workstations. VSCode made that rather smooth with their Github Sync thing.
Any tips for a smooth transition? Must-haves? Alternatives?
I'm mostly running #KDE #Plasma on #Debian but fear I might need it for work on Windows too at some point.
-
Honestly, I love Microslop's #VSCode #editor. I could do with a little less telemetry and AI bullshit though, so I'm keeping an eye on https://vscodium.com/ - I tried it briefly, but it wasn't simply plug and play, so I'm trying to gather the willpower to give it another go.
As I recall, one of the major issues for me was the absence of reliable configuration synchronization between workstations. VSCode made that rather smooth with their Github Sync thing.
Any tips for a smooth transition? Must-haves? Alternatives?
I'm mostly running #KDE #Plasma on #Debian but fear I might need it for work on Windows too at some point.
@saustrup I've just tried switching to codium, and it's mostly the same. But for both there are just configurations that I simply can't find and it's driving me nuts.
I searched for alternatives and found https://zed.dev and have been trying it out lately. It behaves a lot like I'm used so it's not a big shift. Except for the fact that it defaults to linting code every time you try to save the file.
I'd say I kind of love it, but I'm still adjusting. Give it a try!
-
@saustrup I've just tried switching to codium, and it's mostly the same. But for both there are just configurations that I simply can't find and it's driving me nuts.
I searched for alternatives and found https://zed.dev and have been trying it out lately. It behaves a lot like I'm used so it's not a big shift. Except for the fact that it defaults to linting code every time you try to save the file.
I'd say I kind of love it, but I'm still adjusting. Give it a try!
@benjaminlj @saustrup I love Zed! But for some reason it makes my PC fans go nuts all the time (when the language server is parsing code, I guess), so I can't really use it.
In contrast I barely notice when Codium is doing heavy stuff
-
Honestly, I love Microslop's #VSCode #editor. I could do with a little less telemetry and AI bullshit though, so I'm keeping an eye on https://vscodium.com/ - I tried it briefly, but it wasn't simply plug and play, so I'm trying to gather the willpower to give it another go.
As I recall, one of the major issues for me was the absence of reliable configuration synchronization between workstations. VSCode made that rather smooth with their Github Sync thing.
Any tips for a smooth transition? Must-haves? Alternatives?
I'm mostly running #KDE #Plasma on #Debian but fear I might need it for work on Windows too at some point.
@saustrup One alternative is Neovim, which I personally love. Very close to regular vim, but with better defaults and more modern features - including support for LSPs and such.
Also one can modify practically everything to make it behave exactly as desired, use a starting point for making one's own config like Kickstart.nvim - or use "distros" like AstroVim or LunarVim.
It can also be installed in Windows.
-
@saustrup One alternative is Neovim, which I personally love. Very close to regular vim, but with better defaults and more modern features - including support for LSPs and such.
Also one can modify practically everything to make it behave exactly as desired, use a starting point for making one's own config like Kickstart.nvim - or use "distros" like AstroVim or LunarVim.
It can also be installed in Windows.
@marcusxms I'm a big fan of vim in the terminal, so I'll make sure to look into that - thanks!
-
@marcusxms I'm a big fan of vim in the terminal, so I'll make sure to look into that - thanks!
@saustrup As for "plug and play" I think AstroVim and LunarVim are probably the best options. But even regular Neovim is arguably more plug and play than regular vim due to the defaults.
I also read they're now making parts of the package management native as well, which they previously did with LSPs. Many things start as plugins but then when a good standard is found several of them are moved to core.
-
@marcusxms I'm a big fan of vim in the terminal, so I'll make sure to look into that - thanks!
@saustrup Here's a screenshot of my current setup, in one of Friendicas PHP files. It's pretty messy on the left and maybe too much but that's also not default. It's because it's set to strongly highlight tabs mostly because of Python, but I don't really need that in non-indentation based languages.
There are also examples of feedback from LSPs.
-
@saustrup Here's a screenshot of my current setup, in one of Friendicas PHP files. It's pretty messy on the left and maybe too much but that's also not default. It's because it's set to strongly highlight tabs mostly because of Python, but I don't really need that in non-indentation based languages.
There are also examples of feedback from LSPs.
@saustrup One of my favourite things is the fuzzy finder plugin I've setup to some keybinds - some for finding files in the current dir, some for grepping, some for switching the current directory and more.
This plugin is "Telescope" but Snacks.nvim (which includes many things besides a fuzzy finder) or mini.pick should be more maintained currently.
