- cross-posted to:
- technology@lemmy.ml
- cross-posted to:
- technology@lemmy.ml
Some mix of wrong and right, the exact proportions of which I’ll leave as an exercise to the reader.
Some mix of wrong and right, the exact proportions of which I’ll leave as an exercise to the reader.
The problem I see with this attitude is there are plenty of developers that are trying to develop for RHEL instances that need a specific environment for whatever reason. Originally you could use CentOS for this and then you could use Rocky Linux or one of the other distributions that sprung up after stream became a thing. They’ve taken away that opportunity and they may suffer for it since Enterprise application developers like Jeff will not eat this cost since they do it out of the goodness of their own heart and not for monetary compensation. Unfortunately this could end up stifling a lot of the tools that we use in a cloud setting with Red hat distributions. My company has a requirement that we need the OS to look exactly the same and be extremely stable and stream I don’t think has that capability since it’s a rolling distro and could get hit with a bad package update. It would be quickly patched but that still means down time that I now have to explain to my customers. Instead we might switch to Debian which will stay exactly the distribution it should be until I decide to update it. It can be configured in a rolling distribution but it doesn’t have to be and enterprise admins are not going to use something that rolls that that could possibly expose us to more risk with wild package updates. There’s a reason that while we like Arch Linux, we don’t typically use it in an enterprise setup.