where before we ran into compatibility problems with glibc
I wonder if GNU will ever fix that. Surely at some point they have to say “ok we still think things should be open source but we are going to make it suck a little bit less for people that don’t build literally everything from source on their local machine”… right? Ok maybe not.
AFAIK the glibc compatibility issues were related to very outdated glibc versions. IMHO almost nobody with an old distro (Debian 10 or similar) will be using a modern IDE. I’m using Debian stable (12) which has a much newer glibc than required for remote ssh to work.
Sidenote: half a year ago Microsoft even didn’t bother to inform its VS Code users that they were dropping support for old glibc when they updated their remote SSH extension :) I was one of many impacted users, because Amazon decided to use an outdated glibc in their weird Amazon Linux distro.
I wonder if GNU will ever fix that. Surely at some point they have to say “ok we still think things should be open source but we are going to make it suck a little bit less for people that don’t build literally everything from source on their local machine”… right? Ok maybe not.
AFAIK the glibc compatibility issues were related to very outdated glibc versions. IMHO almost nobody with an old distro (Debian 10 or similar) will be using a modern IDE. I’m using Debian stable (12) which has a much newer glibc than required for remote ssh to work. Sidenote: half a year ago Microsoft even didn’t bother to inform its VS Code users that they were dropping support for old glibc when they updated their remote SSH extension :) I was one of many impacted users, because Amazon decided to use an outdated glibc in their weird Amazon Linux distro.