Can't you just keep using the old version? It's pretty much feature complete after all Edit: yes the article mentions it so it's not nearly as bad as suggested IMO. If you're on an os from 2018 you're clearly not really dependent on the latest versions of everything. In the mean time you could start working on the OS upgrade. I don't really understand the wish for old versions in the Linux world. I use BSD myself whi…
> If you're on an os from 2018 you're clearly not really dependent on the latest versions of everything. I'm on Windows 10 which is from 2015. I want the latest software, but an older more stable OS (not Windows 11 yet). It's true that Windows 10 has had big updates (builds). But maybe that's the right approach?
VSCode Drops Ubuntu 18.04 Support
11–20 of 23 posts
Re: VSCode Drops Ubuntu 18.04 Support
#12This messed with me too. At work our primary development environment is a farm of older CentOS machines. They all lost support with this vscode upgrade. It probably impacts hundreds of people. I had to send out instructions to downgrade and pin your vscode version while we look for a workaround. I get that it isn't entirely within the vscode team's control (Electron chose to make the switch), but even then, it really…
Re: VSCode Drops Ubuntu 18.04 Support
#13This messed with me too. At work our primary development environment is a farm of older CentOS machines. They all lost support with this vscode upgrade. It probably impacts hundreds of people. I had to send out instructions to downgrade and pin your vscode version while we look for a workaround. I get that it isn't entirely within the vscode team's control (Electron chose to make the switch), but even then, it really…
emacs will always be there for you, when you're ready.
Re: VSCode Drops Ubuntu 18.04 Support
#14Can't you just keep using the old version? It's pretty much feature complete after all Edit: yes the article mentions it so it's not nearly as bad as suggested IMO. If you're on an os from 2018 you're clearly not really dependent on the latest versions of everything. In the mean time you could start working on the OS upgrade. I don't really understand the wish for old versions in the Linux world. I use BSD myself whi…
> If you're on an os from 2018 you're clearly not really dependent on the latest versions of everything. I'm on Windows 10 which is from 2015. I want the latest software, but an older more stable OS (not Windows 11 yet). It's true that Windows 10 has had big updates (builds). But maybe that's the right approach?
On Ubuntu both the OS and software packages are frozen in time and fixes are backported from newer versions.
It's not the same at all as what Microsoft does. In fact Windows is de facto a rolling OS, a phenomenon which also exists in the Linux world but is much less popular there. A rolling OS user would not have the problem in the article.
Re: VSCode Drops Ubuntu 18.04 Support
#15Can't you just keep using the old version? It's pretty much feature complete after all Edit: yes the article mentions it so it's not nearly as bad as suggested IMO. If you're on an os from 2018 you're clearly not really dependent on the latest versions of everything. In the mean time you could start working on the OS upgrade. I don't really understand the wish for old versions in the Linux world. I use BSD myself whi…
To be fair, Microsoft doesn't support VSCode on BSD anything (and likely never will).
'Support' is a hollow term when it comes to Microsoft anyway. I deal with their paid 'premium support' regularly at work. It's double outsourced, first to Accenture and then to a ton of tiny companies that know nothing.
I get so much better support from the FreeBSD package maintainers than I've ever had from Microsoft :)
Re: VSCode Drops Ubuntu 18.04 Support
#16Is it not possible to just update glibc ? https://sourceware.org/glibc/sources.html
Re: VSCode Drops Ubuntu 18.04 Support
#17This messed with me too. At work our primary development environment is a farm of older CentOS machines. They all lost support with this vscode upgrade. It probably impacts hundreds of people. I had to send out instructions to downgrade and pin your vscode version while we look for a workaround. I get that it isn't entirely within the vscode team's control (Electron chose to make the switch), but even then, it really…
Ubuntu 18 went EOL on May 31, 2023 so about 8 months ago. What CentOS are you running that's still in support and was affected by this change? I had to upgrade all my systems last year after the EOL as most python packages dropped 3.8 support.
Re: VSCode Drops Ubuntu 18.04 Support
#18Ubuntu 18.04 is EOL, unless you pay for extended support. How many people are paying for that support? I hope the people complaining about the VSCode incompatibility aren't people running EOL software and complaining that other people aren't keeping their software compatible with it. I upgraded a number of servers to Ubuntu 20.04 because Ubuntu 18.04 was EOL. I also upgraded my desktop to Debian 12. ;-)
Re: VSCode Drops Ubuntu 18.04 Support
#19Is it not possible to just update glibc ? https://sourceware.org/glibc/sources.html
Not on the system as you'll likely break ABI compatibility and need to recompile everything that uses glibc (basically everything), and LTS distros (e.g. CentOS, RHEL, Ubuntu LTS) guarantee binary compatibility during the release so this isn't feasible.
Re: VSCode Drops Ubuntu 18.04 Support
#20This messed with me too. At work our primary development environment is a farm of older CentOS machines. They all lost support with this vscode upgrade. It probably impacts hundreds of people. I had to send out instructions to downgrade and pin your vscode version while we look for a workaround. I get that it isn't entirely within the vscode team's control (Electron chose to make the switch), but even then, it really…
touch /tmp/vscode-skip-server-requirements-check
patchelf --set-interpreter /opt/glibc/lib/ld-linux-x86-64.so.2 --set-rpath /opt/glibc/lib:/opt/glibc/lib64 ~/.vscode-server/bin/*/node Warning: you’ll need gmake and all the gnu tools for building, make sure to ../configure with —disable-werror