@firstname.lastname@example.org the main question for me is if the "old" #Emacs will be a problem for me. Emacs in Flatpak was pretty quirky when I tried it, and even if it would work great it would be inconvenient as my workflows now depend on Emacs launching containers a lot (e.g. to run LSP servers and tests).
Fedora Workstation is an option of course, but feels silly for _one_ program (even if it is Emacs).
@emacsomancer @email@example.com yup, if that's the only application that's an issue with using a longer term release distro I might just compile my own Emacs.
@emacsomancer @firstname.lastname@example.org yeah, wouldn't think so. I guess I will do it the minute I find something lacking in Emacs 26, which is what RHEL is currently on. It's not _that_ old, so maybe I won't even notice the difference ...
@emacsomancer @email@example.com the main thing is the JSON parsing performance improvements, since I use LSP a lot. I guess I'll find out soon if it's fast enough anyway.
Managing the compilation/installation of a few programs you particularly care about is entirely reasonable. You can also keep multiple installations around if you want to check on old vs new behavior.
@tfb @emacsomancer @firstname.lastname@example.org sure, it's just that when I switched from Ubuntu to Fedora Silverblue I dropped a rather large set of Ansible playbooks to set up a lot of development stuff in my home directory. I'm quite wary of getting back into the same situation.
That said a year of living in Silverblue and doing almost all development stuff with containers has maybe immunized me against that somewhat.
"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko