You didn't have to convince me that using Flatpack is awful, but now I have one more written evidence of just how awful it is. Unfortunately, I too need to modify evdev file to get the keyboard layout I want. I'm not going to build RPMs to do that.
Unrelated to above, my last experience with Fedora some years ago was running fedup only to discover that it had some Python syntax error on an unlikely path (something like a misspelled error type when handling errors) which broke mid-upgrade. And that was probably the third upgrade which broke the system to the point that wiping and starting fresh was easier than trying to fix the broken parts.
My experience is likely very out of date though. Today, I maintain software that deals with configuring and installing RHEL / CentOS / Rocky / SLES (but not Fedora). I don't know if I want that approach to be the approach I use on my personal computer. I don't like the tooling. There are too many levels in it, and every now and then it breaks in the ways that are very hard to deal with (eg. the BerkleyDB code of RPM stores some cursor information into its database and tries to reuse it on subsequent launches, but fails if some part of the database was modified while not touching that cursor, which invalidates it). The later isn't usually a difficult fix (just delete the whole database state file), but it's annoying that this problem has been there for ages, and if this happens as a part of some other automation step, then this may put you in some half-finished state hard to make progress from. Similar problems with getting dnf to reliably discard some stale info.
Also, I feel like the distro doesn't have a "character". I mean, if I want new shiny stuff, then I'm not getting that. If I want old reliable, still not getting it. Great flexibility? -- still no. Great defaults that need no intervention? -- still no. It's an OK distro, but there's plenty of that around.
Unrelated to above, my last experience with Fedora some years ago was running fedup only to discover that it had some Python syntax error on an unlikely path (something like a misspelled error type when handling errors) which broke mid-upgrade. And that was probably the third upgrade which broke the system to the point that wiping and starting fresh was easier than trying to fix the broken parts.
My experience is likely very out of date though. Today, I maintain software that deals with configuring and installing RHEL / CentOS / Rocky / SLES (but not Fedora). I don't know if I want that approach to be the approach I use on my personal computer. I don't like the tooling. There are too many levels in it, and every now and then it breaks in the ways that are very hard to deal with (eg. the BerkleyDB code of RPM stores some cursor information into its database and tries to reuse it on subsequent launches, but fails if some part of the database was modified while not touching that cursor, which invalidates it). The later isn't usually a difficult fix (just delete the whole database state file), but it's annoying that this problem has been there for ages, and if this happens as a part of some other automation step, then this may put you in some half-finished state hard to make progress from. Similar problems with getting dnf to reliably discard some stale info.
Also, I feel like the distro doesn't have a "character". I mean, if I want new shiny stuff, then I'm not getting that. If I want old reliable, still not getting it. Great flexibility? -- still no. Great defaults that need no intervention? -- still no. It's an OK distro, but there's plenty of that around.