I'm glad you have found Fedora to be very stable. It's something we work very, very hard to accomplish. Fedora has long-since stopped referring to itself as "bleeding-edge", though. We've adopted the term "leading-edge" instead, which we intend to mean that we always try to ship the latest stable version of software, rather than in the early days where it was always the latest version. (There's a subtle but important difference there).

As for the non-free software, device drivers, etc.: I really wish it was just that simple. We have had lawyers working for years trying to find a way to do that, but the simple fact of the matter is that Fedora's sponsor is Red Hat, Inc. which is incorporated in the USA. A lot of really terrible laws are in place in the US that mean that if we even tried to do what you are suggesting, it puts us at risk of something called "contributory infringement". Basically, it means that we can be sued in the United States for every person that uses a script we provide for acquiring non-free software in a way that constitutes infringement. For most other distros, they usually just take the risk because they don't have a wealthy backer that could be targeted by patent lawyers. For Ubuntu, they incorporated in the Isle of Man tax-haven specifically because they don't have a treaty with the USA that would get in the way.

As for SELinux, I've been running with SELinux in enforcing mode as a developer for the last seven years. It has been a very long time since it stopped me from accomplishing anything I should be expecting to have work. Occasionally there are bugs in it, but with the advent of SELinux Troubleshooter, I can click a button to allow the action for the moment and send a bug to the SELinux developers who will update the policy, usually within a week.

SELinux has come a long way in the last few years, and I think you'd be surprised to see how much less obtrusive it is. Most people I know that have it turned off have simply done so because they've been doing it that way for 5+ years and have simply assumed that nothing has changed.

Wow. Thank you for this informative comment. I didn't know about all these legal complications.

As for the SELinux stuff, yeah I know it's come a long way and I've been meaning to learn to use it at some point. I even bought a book a few months ago!

Thanks for your work on Fedora :)

SELinux by default has gotten a lot more usable over the years, so that in most cases, the only thing you need to know about is "setsebool" to turn the can_network_connect boolean on for Apache processes (in my practice, anyway).

It's worth leaving running, and much easier than it used to be.