From a quick look at RHEL10 reslease notes, I’d say it looks ok for infrastructure servers, but there are some quite drastic changes for clients, e.g. people who use gui, desktop, workstation.
Just to make it clear, some off the applications mentioned above won’t be fully gone,
as @Ritov already says, there will be served as Flatpaks (directly hosted by RH for RHEL, and very most likely by this project for Rocky Linux)
Not the Flathub once, but the maintained one, i.e. Firefox ESR
I doubt that anything will be served from RedHat. Recently they stated
The Inkscape and LibreOffice Flatpak images are deprecated
The rhel9/inkscape-flatpak and rhel9/libreoffice-flatpak Flatpak images, which are available as Technology Previews, have been deprecated.
I think that the gap can only be filled by the community (EPEL) / devs of the applications, but
I can also imagine that a large customer of RH could put some pressure on this issue …
That’s the “some” part, we don’t know what will be migrated yet.
They are already testing with image builds for 9 at least
And yeah I can imagine that there won’t be a lot of interest to pick up maintaining i.e libreoffice in EPEL, it’s a lot to maintain, while there is a maintained flatpak in Flathub
Which is probably Red Hat’s rationale too. Why commit to maintain something (complex) that is already actively maintained (for now) by someone else and is not part of “essential core” of RHEL?
I think here is a big misconception. In the broadest sense, we are using a RH product, and in terms of contribution, RH did and is doing more then any other firm. Lately they contribute a comprehensive container tools collection to the Cloud Native Computing Foundation (podman and buddies). What I’m saying is that there are others who should rather get such a dislike … (I’m not affiliated with RH).
I’ve used Linux since kernel 1.2.13, and RHL from 4.x, through RHL9, then RHEL2.1 to 9.4 so far. My career, my startup, my success, my leisure time, has been connected to RHL/RHEL since then; even when I worked at a different multinational OS vendor with its own Enterprise Linux. I’ve got friends and colleagues in dev, sales and product management within RH, connections that go back 25 years from 07974 and that company.
When I say we should avoid RedHat, I mean the Company, or as much as we can, despite using an OS release that is still connected by blood and genes to the very entity which forced its existence. I mean we should avoid every other infected cow they fling over their walls at us, and so until OpenELA either crowns or becomes the canonical root distro for EL, at least we can try to avoid post-spacewalk satellite, ansible (sorry mike; james’ was better), lennart’s plague and a hundred other things tipped out of the evil petri dish they think is a well of inspiration.
We know the face of our father, but thanks for checking. Sorry I wasn’t clear.
Yes- I’m not ‘new’ to Linux - ran Ubuntu since 9.0 - but most difficult thing with RHL is nothing is ‘seamless’ like doing the upgrades in Ubuntu. Right now I have everything running well in Rocky 8.10 - so I think I’ll run it out until its support ends!
What you see is not necessarily what you get. The upstreams are not normally supportable at their source.
RH paid full timers at “Fedora” to do the upstream merges. It’s almost a year ago they redeployed those developers to attend to big Iron priorities and it’s inconceivable a part time volunteer or even a number of them can match what was done by those ‘Fedora’ developers working in lock step with RHEL.
The Libre office polyglot by itself when listed then was enormous. The list provided here is in fact the declaration of war of liberation of endusers against the tyranny of exclusion by licenseware optimisation.
Users must define themselves by the apps they desire first and then kernel mongers may compete on satisfying our lists.
Not the other way around.
When surfing the web with Netscape, editing an image using gimp or inkdrop, or a video via shortcut, or a document via libre office the last thing in mind is thanking Big Rust for making it happen through peephole credentials.