One issue with rollbacks Arch has is that there's basically only up to three valid configurations available at any time. These are your current system configuration (oldest state), upstream repositories (newest) and your local database copy (somewhere in-between, though all three states can be identical, e.g. straight after Syuing). By definition, you can't convert your system configuration back to an older one because it's the oldest one of the three already. What you can do is mix your current oldest configuration with packages from the cache, older or newer doesn't actually matter. But you're not getting back the old state really, you're creating a new one that's different from Arch's repository.
A configuration on NixOS includes all exact package versions and their exact configurations. No exceptions.
If you actually need these guarantees is a different question. I used Arch for 15 years and never had significant issues. I switched to NixOS instantly after trying it on an old notebook and immediately recognized that the whole approach suits me so much better that I switched almost all machines over by now.
It's basically the same time I started using Linux somewhat more. I didn't go Windows-free until 2007 though and then returned to Windows because I needed it for something with my Master's thesis. I kind of shudder at the thought how my old setups looked under the hood. You learn a lot in 18 years... Probably copy-pasted a lot of shell commands back then. But UT2k4 in its OpenGL glory was worth it
I don't even understand why they make that distinction. I recently bought a used notebook with Windows 10 preinstalled that can't be upgraded. But if you just boot up the Windows 11 ISO it works fine without issues from there.
Granted I don't know why someone would want this; I was genuinely surprised when I noticed installation without a Microsoft account isn't supposed to be possible. Then you get that system that just feels sketchy to use, Teams in autostart, online services in your menus and all that. And that's just the stuff you can see. It's a total disaster in my opinion. But it went downhill ever after Windows 7 as far as I can tell.
In recent years that seems to be eating into every major OS… but six months into the pandemic, Mozilla laid off the entire team, killing its next-gen rendering engine, Servo.
(Much of Mozilla's revenue comes from Google, of course. This couldn't be because Rust was, and is, outshining Google's GoLang? Surely not?)
How does one even make that connection? Why would Google be interested in such a topic? I'm pretty sure GoLang doesn't make them money directly, but rather as it streamlines their in-house work. I don't think they profit off this even a tiny bit.
Also GoLang, while probably not a better language in every aspect, has some very neat properties which set it apart from Rust (and vice versa).
One issue with rollbacks Arch has is that there's basically only up to three valid configurations available at any time. These are your current system configuration (oldest state), upstream repositories (newest) and your local database copy (somewhere in-between, though all three states can be identical, e.g. straight after Syuing). By definition, you can't convert your system configuration back to an older one because it's the oldest one of the three already. What you can do is mix your current oldest configuration with packages from the cache, older or newer doesn't actually matter. But you're not getting back the old state really, you're creating a new one that's different from Arch's repository.
A configuration on NixOS includes all exact package versions and their exact configurations. No exceptions.
If you actually need these guarantees is a different question. I used Arch for 15 years and never had significant issues. I switched to NixOS instantly after trying it on an old notebook and immediately recognized that the whole approach suits me so much better that I switched almost all machines over by now.