Comment by CGamesPlay

Yeah, this works. Two drawbacks: you have to rebuild the container when the port forwarding configuration changes, and the port forwards have to be unique on the entire machine.

> which unfortunately I’m becoming increasingly reliant on, even though it’s gotten me into trouble with larger projects

You could… not do this. You know it causes you problems, you consider it unfortunate that you’re becoming more reliant on it, and yet for some reason you’re choosing to continue anyway. Why are you doing that?

Just tried it... and it says it's client-only, but when I try to run the SSH provider using my Rapberry Pi it says it needs `docker` to be installed on it :/. So it's not just client-only, is it?

It's proprietary software masquerading as open-source, for one, and intentionally fosters dependence on its vendor for the plugins that support the most popular languages as well as key features (remote editing, WSL support, integration with the mainline plugin repos), for one.

Microsoft injects proprietary spyware into the official builds that you can't see from the source code. You can get unofficial builds of just the source code from the VsCodium project, but Microsoft blocks your ability to install a lot of extensions if you don't use the official build.

It’s clumsy as hell. It’s neither a good editor, which focus on being fast when doing things with text, nor a good IDE, which is more about the tooling and getting a project done. It’s trying to be both at the same time. And the result is bad at both.

Ultimately, they're about as trite as reasons to hate Vim or Emacs. It boils down to preference, and I'm outlining a path to using another editor and getting access to some of the same features.

Each time I try to use it, I find myself distracted by the impulse to fix the bugs that I notice. There's always this moment when I find a comment from myself, several years earlier, in an issue that's still open because it's unclear whether it's a VSCode problem or a plugin problem, and it's like: "oh, here I am again, doing this instead of working".

That's not to say it's especially buggy, it's just so large, there are a lot of places for bugs to hide.

I get distracted by the impulse to contribute to other editors also, but those are contributions that I'm happy about. They don't always result in bugs fixed or features added, sometimes somebody says "no" but at least it resolves in some way. With VSCode it feels like I'm going in circles.

I personally feel some inner sense of dissonance when I use software written in Electron when alternatives are available. Software targeted to the technical audience has no valid reason not to aim higher in terms of performance and fundamentals.

I will give you one reason why I don't like it much:

- The push to use Github Copilot and no option to disable that crap.

I wish there was a fork of VSCode with all the telemetry and all of the proprietary crap disabled with 100% extension support...

I do not hate it when others are using it (none of my business). But I do not like to use bloatware. Text editor that eats RAM (even excluding LSP) like 3d editing software.

Microsoft ?

Through the use of amazing PR they have made people forget about their Embrace, extend, and extinguish strategy with open source.

Just so you know, the devcontainer VSCode extensions are considered proprietary by Microsoft and therefore not allowed to be installed in VSCodium. There are some open-source container plugins, but they are all a bit janky for the container use-case in my experience.