If you want a powerful development/work environment - and you do like what and how Linux provides here - use Linux - but as I was not satisfied with what/how Linux provided I looked somewhere else and I landed in FreeBSD.
Here are some of the reasons and conclusions I came to after using FreeBSD (and also Linux/AIX/HP-UX/Solaris in various jobs) for about 20 years.
Here:
Also - even if I would be forced to use Linux - I would probably setup it with ZFSBootMenu and Root on ZFS - I believe Fedora does not allow any of these?
If you're not the type of person who wants to run FreeBSD as a workstation, none of this will matter to you.
I last ran it about two decades ago, so it's been a while.
Unfortunately, we now have a few people complaining about predictable, consistent behaviour with packaging that is coherent. The base system, FreeBSD, packaged.
The complaints are about the effect of wilful force.
Maybe I'm old-fashioned.
When I force something with my eyes shut (ignoring warnings), I do expect the unexpected as a result of my ignorance ;-)
No your not, even in the Sun-Solaris time they asked themself why rm should be able to delete /.
>The complaints are about the effect of wilful force.
Don't make a function no one uses (because it has no function) but is able destroy the system.
Compare it to a aircraft, shutdown your fuel has probably a emergency function, make a button to instantly destroy your aircraft has no real function nor will it ever be used (aka pkg remove -af).
>Unfortunately, we now have a few people complaining about predictable, consistent behaviour with packaging that is coherent.
That's not predictable but stupidity, try to remove all pkg/Application/Apps from MacOS, Windows, OpenBSD, NetBSD or Android...will the system boot or not? All those operating-systems make a clear distinction from the base-system to "apps" and the system should ALWAYS boot to a state where you can interact with it and so should FreeBSD.
There is not a single system (no OS and no living being) in this world wheres there is a function to destroy itself would not be called a error (the worst possible one)
But hey lets tell Linus (from Linus tech-tips, a Linux beginner) it's your fault because you forgot to read 100 lines, what a wannabe elitist think, there are ZERO point's, that a system should be able to make itself not booting anymore.
Current aims include enhancement of the installer for FreeBSD; KDE Plasma and applications as an option.
How is OpenZFS second class on Linux?
<https://github.com/openzfs/zfs/> is not perceptibly FreeBSD-first.
While You can spend some hours installing Linux with ZFSBootMenu and LUKS encrypted Root on ZFS - there are ZERO Linux distributions that allow ZFS Boot Environments out of the box.
That is the reason 'why' Linux is not the first class ZFS citizen.
There is also the ZFSBootMenu part ...
If you have done this at least once - noted the commands, etc. - it will take shorter - but never shorter then FreeBSD 'Auto (ZFS)' option in the bsdinstall(8) installer where you just select the disk on which it needs to happen and hit [ENTER] key.
Reminder: I neither want, nor need, to check several different guides that cover only the encryption part.
In any case, I'll take additional advice; it's impossible to trust apparently authoritative statements from you.
I'm considering alternatives. Not ZFSBootMenu in isolation. I'm in no rush.
Ahh now i get the point why you have no problems destroy your system with a simple pkg command ;)
Linux does not play nice with batteries.
https://www.ifixit.com/products/lenovo-thinkpad-t480s-batter...
Does the T480 have that much better battery? Maybe I'm doing something wrong haha.