Guix/nix seem very powerful. The reproducibility is something ansible just isn’t built to same level robustness for, which makes them seem very promising to me.

Its use able. I like unified update mechanism and shared package/library/image systems

That’s awesome! Next laptop decided on.

Fedora also has a rolling release version called rawhide

Flatpaks are great for GUI apps, and have a sandboxing system that allow them to work well on any system that support flatpak. This allows devs to package once run anywhere, saving Dev time! It also has a portals system to allow for better system integration of the granular permissions needed for the app to actually work (nobody wants a truly isolated sandbox for every app).

Snap is less featureful for GUI apps, but work closer to how native packages do. The real issue is the proprietary app store required for it, making non-foss. If you want the same benefits of snap, check out Guix and NixOS both of which have a more cleaner design, and work better IMHO.

Dang, Suse really coming in strong with this. I still wish they offered openQA too. Between Rancher, and Suse they really do go pound for pound against RedHat.

The rest, ansible for any sufficiently complex enough setup at the moment. Good for integration work with LDAP, etc if your using that. Again may play around with guix on that front.

I’m a /home on separate drive/partition kind of guy. I like it just following my installs. Though seeing some using guix/nixos to create a config for my desktop has got me wanting to spend a weekend trying that out.

I’m choosing to divest and look for more opportunities to help community ran distros to better fill that niche. Maybe NixOS or Guix as system os and rke2 and flatpak for the rest of services and apps.

The snap store is proprietary, flatpaks handle the graphical app space better, OCI containers handle the service space better, and really high reported load times.

Flatpaks are awesome IMHO.

I’m honestly a big fan. Systemd-init has tons of options like run targets, sandbox options, users you want things to run as, etc. System-oomd has tons of qol stuff for desktop users to help with stutter and responsiveness. I am also kind of excited for UKI that systemd-boot is set to support.

Under the current EULAs as a customer I would have concerns that any attempt of mine to modify software from redhat or continue to use my servers without redhat support would be breach of contract. That is a huge step backwards from companies that embrace opensource.

They actually own centos though, and from my understanding the Fedora org isn’t ran by RedHat, just sponsored.

RedHat is a major sponsor of Fedora, but Fedora is a separate entity, so there is no know plan of them moving away from being a registered public good and no good reason for them to.

Sorry about you getting a duplicate. I was trying to cross post just to places where I saw incorrectly that RedHat was going closed source.

I believe so, and any other “bug for bug” clone of RHEL.

Agreed. Its news for sure, and maybe it speeks to some broader topics (like if the wider linux community wants things what RHEL offers, how would we go about doing that), but this isn’t some Judas kiss to the Linux world.

I am contributing to the topic though, because people are taking it to an extreme looking at even avoiding Fedora, the community ran distro, that have nothing to do in this decision.

Any issues with CentOS stream for your work? Could always switch to Fedora server too if you wanted to keep the same structures and such, but separate some from RedHat.

More detials found here: https://www.redhat.com/en/blog/furthering-evolution-centos-stream?sc_cid=701f2000000tyBjAAI

Seem more accurate that their public repos will be closed, so now only centos-stream will be public. You will still have full access to source through their developer program or as a paying customer.