So you like vscode huh? You probably should read this

https://github.com/microsoft/...

Just updated... remote ssh still works for me... didn't even have to clean out known hosts or edit any .ssh configs

Note: This is on VS Code, NOT on VS Codium which apparently has this bug in remote-ssh

My advice would be to get a real operating system. :)

Tl;dr you can't connect to the remote extension host server if you use an open source build of VSC.

@HiFiWiFiSciFi Microsoft locked remote-ssh for vscodium

@kiki Set up a proper VS Code install? https://code.visualstudio.com/docs/...

That's been like that for a long time. VSCode isn't open source – it's a proprietary product.
Parts of it are open sourced, but the important ones are heavily limited.

The .net debugger for the C# extension can only be used in official visual studio products
Same with the remote extensions

Same with the entire extension marketplace actually....

@HiFiWiFiSciFi mate are you stupid or just pretending all this time?

@LotsOfCaffeine

Um... OP is blaming VS Code for a problem that actually only exists in VS Codium...

Like, oh boy I hope you don't like MS Word... because let me tell you all about this bug in Libre Office.

Which thing is it I'm being stupid about?

@HiFiWiFiSciFi the reading thing

@LotsOfCaffeine From the OP link... LOL

AND I Literally updated VS Code and CHECKED that this bug doesn't exist before I posted.

You sure my reading is the bad one... or maybe... maybe could it be the other way around?

You want me to post my WORKING remote-ssh log? Or we good?

@HiFiWiFiSciFi how can you read these words and somehow come up with "Bug" in your head?

Ah you know what, just don't answer that

@LotsOfCaffeine I didn't use the word "bug" until AFTER you called me stupid. And even then I'm referring to "bug" colloquially... I just literally posted evidence this is not a bug, but a choice made by MS to cut off VS Codium from using the SSH remote plugin.

So if your reason for calling me stupid, occurred after you had called me stupid, maybe its that you're just fucking full of shit.

You white knighting for kiki or some shit? I've never seen you be this daft?

I updated my VS Code to ensure this "bug" did not also exist in VS Code and was limited to VS Codium.

Why you ask?

So that I wouldn't be the one looking stupid for the rest of the thread.

One would need to "get a real operating system" because they are running a shitty VS clone no doubt on linux. It's a joke.

Jesus christ. I'm going over to reddit for the day.

^I love me some dR strife.

VS CODE = VS CONDOM

Why is that of interest for us that like VS code?

Its not a problem if your running vscode, only if you decide to use one of the forks for some reason.

@Voxera well technically it's just an open source build of code (≠ vscode)
But even if you were to build it yourself, or grab another open source build from your local Linux package manager, the issue would remain

Not due to any technical limitation, but rather because Microsoft does some shady license fuckery, to be able to call their product open source and advertise with that. But really they don't want people forking their product and being successful with it, hence a lot of the important tools are locked behind this project branding.

I think that's why Kiki posted this, it's more a matter of principle I would say.

@LotsOfCaffeine @HiFiWiFiSciFi @Voxera

Correct me if I'm wrong, but this is not about bugs or usability for individual users.

It's about open source advocacy, about the fact that a lot of people call VSCode "open source", while Microsoft does some things which would make Stallman cry (more than he usually already does).

It's just a red flag, that just like Chrome/Chromium, VSCode is more of a semi-open product. There are certain stakes behind its development which are not fully compatible with FOSS-philosophy.

One of those stakes is user research data. You can choose to use a telemetry-free fork, but Microsoft says: If you don't give us your data, we won't give you our plugins. And without plugins, VSCode is basically just Notepad with a dark theme.

That is all. You're not a terrible person for using it, it's just an FYI saying "it's not as FOSS as you might have wanted".

But hey, there's always Vim.

@bittersweet exactly

I've been meaning to learn vim or a comparable editor for a while, but i feel like just getting basic IDE-like features can be quite a hassle to config

@bittersweet exactly

@LotsOfCaffeine but its not the vscode license that puts up restrictions but the remote ssh plugin.

Sure both are ms products but they are different products.

So its not any shady licensing.

And Stallman will consider most of MS practices bad.

But in this case I think its more a a failure to actually read the license before getting and trying to use it.

MS is a company with a goal to make money.

They offer some parts for free and others they either charge for or keep to their own eco system.

If you have a real problem with that, just do mot use their products at all, don’t come crying because they did not give you everything you wanted completely free ;)

@Voxera It's just the marketing that pisses me off.

They pat themselves on the back that they're all open source and microsoft <3 linux bla bla

but one of the most important features of vscode, the extensions, are only to be used their "official" build with all its telemetry

And the remote development, the .net debugger are in a similar situation, it's the things that elevate vscode from a badly performing editor to a highly extendable development environment.

Edit: if you wanna do C# on an open source code build you can use Samsung/netcoredbg as an alternative to the proprietary debugger from ms

@LotsOfCaffeine its not extensions as such but specifically some of ms own plugins that have this limitation

But there are quite a lot of other plugin developers, why not use one if them?

Could it be that ms plugin is just a bit better?

Personally I use vscode for react and typescript and the community version of visual studio for c# and that is free to use but not open source.

I feel this is more about MS bashing than any real wrongdoing by MS.

@Voxera the entire marketplace is shut off for open source builds
You can work around that, but that breaks EULA.
This is also the reason open vsx exists.
See https://github.com/Microsoft/...

And yes this is a Microsoft bashing, they deserve it.
Except the people who designed the C# language.