• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • nixOS , because it's a completely atomic distribution, like a docker container OS style. You define the state of the system in a configuration file, which can even control the kernel, and you can switch to an older configuration file in any reboot. It's more of a pain than the others, but it works ok out of the box and when you fix something it stays fixed so you'll never end up in a situation where something breaks and you can't fix it.

    Also, all the packages bring their own versions of their own libraries and directly link to them so they'll never break during upgrades, but conversely a lot of Linux installers that try to link to system libraries won't work.





  • I’ve thought about it and I’ve decided that I can live with that. Besides, I don’t think it will make it to that level of popularity before “the incident” that shocks everyone and triggers a senate inquiry.

    Either there will be horrific side effects or Musk will cut quality or make an ‘executive decision’ that beams ads into everyone’s head. I don’t know the final implementation, but I think they won’t resist the temptation to make the firmware up-gradable remotely, and once they have that, they won’t resist the temptation to meddle.







  • 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.


  • 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.



  • If I were running a Unity project, I’d be tempted to just jump to Unreal. No matter what promises Unity makes you don’t have any actual guarantee that they’ll keep them while Unreal has the “non-retroactive” clause directly in their contract. However painful the switch is, you’ll only have to do it once.