It's not quite that simple.
Each package can choose one from a handful of runtimes to use, each of which include common dependencies (like gnome or qt libraries), and if multiple flatpaks use the same runtime, that runtime is only downloaded once.
It is less space efficient than your typical package manager, but brings other benefits like sandboxing.
Don't you know anime characters are drawn white because of Japan's "white envy"
Oh, it's a football reference, my bad...
And frequent, if you miss a train, it's barely an inconvenience to grab the next one
Switched from the kde test repo over to baseline Tumbleweed today. It was actually smoother than I'd expected
USA: 128% UK: 105% China: 210%
What's interesting to me is that it seems China had a lot more responses with 2 or 3 answers, where UK, in particular had almost no duplicate responses.
sudo chown <user> -R /path
sudo chgrp <group> -R /path
I'm running kde6 on fedora rawhide kinoite, it's pretty stable.
Minor point of clarification though, kinoite isn't immutable ootb, it's atomic (which is to say it either fully updates or doesn't. Immutable is an experimental setting you can enable though)
I would take that one step further and recommend an atomic release: like fedora silverblue or kinoite for someone new to Linux. The read only base filesystem makes the risk of breaking things basically zero.
It does make some tutorials invalid though, which can be a source of frustration.
Tbh it's possible I messed something up, iirc the bridge network I was using wouldn't work, and it seemed like it would only work in host mode, hence the belief that I needed to remap things. This was over a year ago, and tbh I didn't try very hard to make it work.