A note on the name and version - 14.04 means released in April 2014, and the names go up alphabetically per release (T U V etc).
A note on the name and version - 14.04 means released in April 2014, and the names go up alphabetically per release (T U V etc).
Fedora was one of the first to move to chkconfig-style scripts, and it was one of the first to systemd. It sort of forces you to learn new things, even if you don't want to.
The big downside is the updates taper off really quickly, so unless you keep rolling forward, you'll soon end up with an orphan distribution. Fedora is the philosophical opposite of the Ubuntu LTS releases.
I've been running Fedora for over a decade, and while it suffers from being bleeding edge sometimes, I don't think I've ever had stability issues or things I'd describe as a buggy mess.
Fedora would throw kernel panics on seemingly-minor things. Things like starting Xfce instead of GNOME3, for example. Things like running for more than 15 minutes. Silly cases. The hardware was not the problem; it handled Slackware (a non-systemd distro) and openSUSE (a systemd distro) quite alright. Because it handled openSUSE alright, I knew it wasn't systemd itself either (though that certainly didn't help).
Fast forward a year or so, and I'm investigating using Fedora in order to leverage FreeIPA to authenticate against an Active Directory environment. Fine and dandy for all of three days, after which Fedora magically forgot all my network settings without any explicable rhyme or reason. Switched back over to openSUSE (which also has AD integration features - and much more polished ones, so I found), and everything worked fine for several months (after which I ended up finding a better job anyway).
To put this in perspective, I've found everything from Debian Sid to Arch to Slackware-current to openSUSE Factory significantly more stable than Fedora. I've also found RHEL and CentOS to be significantly more stable than Fedora. By some god-forsaken Beefy Antimiracle, Fedora somehow manages to fail even harder than Softlanding Linux System (which - if you know your distro history - was so awful as to cause Pat Volkerding and Ian Murdock to create Slackware and Debian (respectively) in a desperate bid to give people good reason to not use Softlanding Linux System). That's absolutely depressing that an ancient and horribly-designed distro from 1993 running on my ancient Compaq Presario 1210 runs better than a supposedly-modern distro like Fedora.
I've had way more trouble with out of date packages on Ubuntu than Debian (Sid).
Just my two cents, but I've had way more trouble with missing packages. It's a pity, but Ubuntu repositories are growing at a much faster pace.
If I want the latest and greatest I can always compile from source...
I think a lot of us have had mixed experiences. I've had some that were awesome, but some that made #python look like a hippie drum circle.
(Of course, sometimes #python is a hippie drum circle, but that's another conversation.)
Arch linux (actually I use a spin off called Manjaro) seems to be a lot better in that regard.
I've always liked Arch. I'll give Manjaro a look at some point.
"Oh download this script, and run it as root", or "Edit this file and paste the following". With no real understanding or awareness.
That said, as a Slackware user, I'll admit to the Arch wiki being one of my go-to stops for reading up on how to tweak some program or other; Arch's wiki and the Slackbook are both on pretty equal footing for the closest things the GNU/Linux world has to OpenBSD's manpages in terms of complete and comprehensive documentation on ever last facet of the underlying system.