I get that it isn't entirely within the vscode team's control (Electron chose to make the switch), but even then, it really interferes with a lot of people's daily development needs. These systems aren't particularly old or out of support.
I get that it isn't entirely within the vscode team's control (Electron chose to make the switch), but even then, it really interferes with a lot of people's daily development needs. These systems aren't particularly old or out of support.
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
emacs will always be there for you, when you're ready.
CentOS 7 goes EOL June 30th, so you're pretty close to their end of life (CentOS 8 stream has 2.28, so should still work with the new vscode version, which is why I'm guessing you're talking about 7.)
If you don't already have plans for replacement/upgrading, you really need to have plans.