This is good distro for developers by developers. I wouldn't suggest it for everyday users though. There are too many beta quality bugs since it uses really bleeding edge releases.
Fedora isn't cutting edge compared to actual rolling release distros so if that's still too much for you then RHEL or CentOS should be enough.
It kinda depends upon what you're doing with your computer. E.g. if I weren't into gaming I would be using CentOS over Fedora (or Ubuntu).
It is a pain to build it at all, from the sources. With the exception of the apple/swift repo, all the other apple/swift-* repos do not even seem to have tagged releases. At least not in the sense that other projects do releases.
-Cron jobs don't run
-Package manager creates multi-gigabyte log files
-Package manager crashes on systems upgraded from previous releases
-GNOME crashes when switching to a virtual terminal and back
-Default bluetooth config doesn't work for some devices
-Ethernet runs at 10mbps instead of 1gbps
Bluetooth (Bluez) is a trainwreck on any distro; even the version shipped with Ubuntu 18.04 (LTS!) is broken.
Broken BT support in a Windows context generally means poor drivers for a given device - at least the Windows 10, which is almost 4 years old, has a stable BT stack. Therefore, BT problems are of particular (per-device) nature.
In Ubuntu, the problem is systemic, due to (even ignoring how terrible the BT protocol is) both Bluez's (alleged) terrible engineering practices, and Ubuntu's utter carelessness of the area. In this terms, BT problems are of universal nature.
For example, the 18.04 Pulseaudio/BT configuration is broken by default - see https://askubuntu.com/a/1050172.
This is not an exception; the Pulseaudio/BT configuration has been broken in a way or another since... forever. Very evidently, the Ubuntu devs prefer to ship a broken-but-up-to-date BT stack, than a working-but-old one.
For a more historical perspective of the Ubuntu/Bluez trainwreck, see http://www.bennybottema.com/2010/08/08/how-ubuntus-broken-bl.... Summary: "Bluez is a bunch of cowboy coders is why".
Though I have yet to see any BT implementation that isn't at least a little bit broken. Nobody actually conforms to the spec so you have to attempt to make your noncomforance work with the widest possible variety of other vendors' nonconformance and you'll always find device combinations that just don't work together.
Also, Fedora gets new kernels all the time, and that often takes care of problems that sometimes persist in more "stable" distributions.
I have one mid-level issue per release, I figure, and it is usually patched within a couple of weeks.
I did have a bad experience upgrading from F27-29, so I've only been on F29 for maybe a month or so, and it has been smooth so far. I will probably wait a few weeks to a month to upgrade to F30 to increase my chances of a trouble-free transition.
dnf could definitely work on keeping its generated garbage down to a more reasonable size, though.