When is Rust going to have a stable distro experience?

Thanks, Daroc. Appreciate you chipping in.
In this case, rustup is *not* yet available in debian stable.
https://packages.debian.org/search?keywords=rustup
Shortly it should be available in trixie; and I've already got a pair of nodes running testing and unstable respectively.

And yes, I'm aware that the artifacts rustc generates are "static", that's part of the problem.

> Rust libraries from years ago are compatible at the source level with modern libraries, not at the binary level, but you would hardly notice that given that they're all statically linked.

Yeah, except for the minor problem that *I do notice that*, particularly in the case of building game engine artifacts.
For *that* side project, we still have a ubuntu 18.04 node set aside to do builds on due to it's lower glibc version (2.27).
All of our steam builds run across distros, and only musl-based distros need special attention.

The other problem is, I'm not a "coder". I can read most of the ALGOL-syntax derived languages (All the languages that like parameters in parentheses) and even write some functional if or switch blocks. But at best, I'm just a scripter/automater. I invoke other tools/objects, because I don't consider myself competent enough to write my own, nor do I consider it a good use of my time.

> That said — yeah, chasing down things that break is really annoying. I definitely sympathize. The user-experience for these things is in tension with so many other goals that it isn't nearly as good as it could be if it were the subject of everyone's focus.

At best, I'm skilled at packaging. I used to roll my own spin of ubuntu ISOs with Xen and TORAM=Yes, but they've made that progressively more difficult to the point where chromium became a snap without a backing .deb, so I just gave up trying to work with canonical and lubuntu, and went back to debian. Lots of foolishness around openvswitch and ceph because they were pushing openstack hard, and I didn't want that kind of enterprise girth for no good reason. So many packages moving to docker-compose, like Sentry. Same nonsense happening now in homeassistant; they're abandoning pip installs for their HASSOS docker minimal "distro", and I've found it's nearly impossible to debug problems.

It's a mess, a proper clusterfsck that nobody seems willing to crawl back out of, just add more layers to make it worse.
Hardware Virtualization has been around in every x86-64 for what, *twenty* years now? Everything has moved to PCIe, and Xen does one thing and does it well, manage access to PCIe devices. And yet we're still arguing over vulkan and wayland and AMD drags their feet with GIM (GPU-IOV Module) to enable split functions on consumer hardware... Let alone nvidia's disdain for linux and vGRID license greed.

I'm still kind of wary of BPF, still rather annoyed that io-uring is "Barely" made use of, still peeved that kdbus flopped and there's still no sane RPC mechanism besides "well, maybe you can cobble it together with openssh or grpc?", still waiting for wireguard support in embedded devices (ESP32), still chomping at the bit to make use of pidfds and the new mounting syscalls... Still waiting for /proc to die, still praying for perl to finally be buried and laid to line noise rest, blessed be thy commented code...

*sigh*