How do you prefer to install compilers, interpreters, sdks e.t.c

Definitely stick to the OS package manager. Not doing this is a mistake a lot of devs make.

Otherwise you end up with an app that doesn't run on most systems, and expecting people to do curl piped to bash as root.

Stick to the stable branch. Stick to the OS repos.

uninstalling sometimes doesn't work when you install from source, so i've learned to be patient and always use the distro package.

For personal use, I previously used system packages, but now I'm installing them through nix home-manager. It's really nice, especially because I've got a list of them now and don't have remember what to install ever again.

I use Nix, even on my Ubuntu machines, to install tooling in my user profile.

Nixpkgs unstable stays pretty up to date. The few I want something on release day or bleeding edge nightlies, I override the derivation source. I use nvfetcher to pull the latest release or head of the default branch as part of my update routine.

I'm pretty new to Nix, so its been slow integrating into my workflow, but I plan to start integrating flake's into my repos. My team seems to have constant issues with keeping their tooling up to date which breaks things locally from time to time.

nixos, I use devshells with flakes (and direnv)

Depends what I am working on.

Sometimes I have to work with a mess of angular and node versions, which I don’t want polluting my main system and be something to need to manage. So I use containers for development and have all dependencies for that specific project in the container

I use stuff like Rustup, in a Distrobox dedicated to the work area.

+1 to running whatever is packaged by your distro. For me, Fedora is rarely out of date. If worse comes to worse, you can always volunteer to become a packager and improve the ecosystem for everyone while fixing your own problems.

I usually use a version manager to install those stuff so I can install multiple versions when I need it. asdf is my first choice because it support a lot of languages via its plugin system, and the list of plugins is huge.

Usually distro packages, even mingw and android's sdk are packaged now (at least on Ubuntu which i'm forced to use).

Not shying away from upstream though.

I use Arch BTW, so no problem with outdated packages. ;)

I avoid using distro package managers

LOL

I'm a big fan of Condaforge for this sort of thing. Keeps my development software separate from my daily driving software.

I run Ubuntu and use the Nala frontend for APT to keep a log of my package installs. That way, I can easily remove everything if I no longer need to work with a particular language or set of dependencies. For anything too complicated, I like to drop into a Docker container (which integrates nice with VSCode/Codium)

Since I run Fedora, the repos are very up to date. Not as bleeding edge as Arch may be, but plenty fine for learning and development. There are a lot of issues you can run into during manual installation/uninstallation, so I always use distro package managers. Plus, that ensures that software has a much greater chance of running in an environment similar to an end user, so it's just ideal overall. I can certainly understand frustrations with Debian packages being out of date, but that's an ideological choice, and the user should have been aware of that before choosing Debian. All I usually have to do is install the compiler/runtime, a language server for neovim, and some minor configuration for IntelliSense, then I can be up and running with a new language.

The other side to this is that you don't necessarily need to be using the latest version of the language to learn or develop in it. It's often a good idea to stick with the latest LTS release of the language so that it's most available and compatible with the runtime/environment that the end user has access to. Utilizing features only available on bleeding edge versions of the language can make it difficult for others to use your software, as they'd have to go through the hassle of manually installing the latest version, and can lead to breakage if the language changes before the next stable version is released.

Don't do that. I would use distrobox with a Fedora container

The only "compiler" I need is npm... Usually just use the one from the repos, however if it's too old, which on most stable distros it usually is, I install a tool, called n from the old version of npm and use that to update npm...