More nixOS development. It's the reproducible builds on the OS scale, one configuration file that will always generate exactly the same system when run, and you can update and rebuild from that file without restarting the system in most cases. This should make triangulating and fixing distro issues much easier, as well as making a distro easier to maintain from the user side.
Yes, and every package specifically defines the exact version of its libraries that it needs and the system symlinks everything together package by package, so there's no chance than an update will break something further upstream. The configuration file also controls things like MySQL configuration and user permissions so you can get literally the exact same system. I think even docker doesn't control for library versions with its regular configuration.
EDIT: And it keeps older versions of the configuration file and its symlink arrangement around, so if something goes wrong, you can reboot the machine and select an older version from the bootloader.
Better than Docker in terms of reproducibility. While Docker containers are usually more or less reproducible, Docker images are not as the Dockerfiles depend on lots of external state such as the repositories of the distro used as a base image. This is also partially true for NixOS, but it's far more realistic to pin a version of nixpkgs (the Nix(OS) repository) than do the same with Debian repositories. The new Flake format even provides a way to pin nixpkgs by default.
I don't realistically expect to see any progress here but video hardware acceleration gaining first-class support in popular applications would be a nice dream. The one area Linux is complacent to be "inefficient".
One of the KDE devs has been working on some magic that might keep application state even after the desktop crashes.
Note that Input Leap will be supported on a Wayland session in GNOME 45 / Fedora 39 thanks to the new InputCapture portal and Peter Hutterer's libei work.
Barrier seems to be dead upstream and Synergy is closed source though, so those 2 probably won't get updated soon
Polonium - autotiling for KDE 5.27. Ever since KDE Plasma broke Bismuth on wayland, i've been running with bare Plasma. Polonium is the first project to work (mostly) as Bismuth used to, although it's just one developer working on it as far as i understood and it still has a bunch of bugs. But really looks promising.
Also, KDE 6 (which will break everything again probably) :D
Allows me to interface a PC to a canbus in an efficient manner. I wrote an autopilot in perl using that, but I would like to see the project mature to the point where it is stable enough for production environments.
Hetzner's reliability is starting to be questioned, and their verification process seems to be a pain. In not going to put critical loads up there anyway, so I suppose it's fine. Thanks
My apologies, V is a new programming language based on Rust, Go and some others. I've been learning it a bit, and its fairly easy to learn, so i hope it has a bright future :)