I already use Fedora Workstation and am familiar with the environment, install, and setup process. CoreOS' "happy path" seems to be cloud (or at least hosted in a hypervisor) -native, and that was not the target here. There seem to be external dependencies on installing it to bare metal I didn't want to mess with[1]. I installed Fedora Server from .iso almost exactly the same way I've installed Fedora (workstation) many times.
My "day job" uses rhel, and with the recent CentOS end-of-life debacle I'd like to stay both FOSS and .rpm-compatible with rhel. I don't know for sure, but I think CoreOS is a different "vertical" than the fedora/rhel/centOS family.
I'm generally wary and suspicious of "automatic" updates, preferring to control when/how updates are applied to my machines. $ sudo dnf system-upgrade is a well-known quantity to me.
I have a complicated LVM setup, and significant time/effort already invested into LVM. As of F34 LVM/ext4 is still first-class.
CoreOS seems to be targeting cloud/kubernetes as implementation characteristics, and my "one man shop" gig is the anti-that. I'm pretty old school - only just started learning Docker about a year ago. I've recently bought into containers as packaging/deployment aids, and using docker-compose to keep deployment in version control. I guess all of this is to say I'm trying to "keep it simple / stupid" and re-use what I already know. Unless CoreOS can give me order-of-magnitude performance gains, I don't know the value prop beats the cost to pick it up.
[1] https://docs.fedoraproject.org/en-US/fedora-coreos/bare-meta...