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.
The browser and desktop and terminal you'll inevitably want to use aren't any more part of that "complete" OS than they are on Linux (and in many ways FreeBSD Ports is more immature / less well-integrated than Linux packages).
Comments
Not OP, but off the top of my head, it's a complete OS, kernel and user land are released as a whole.
I last ran it about two decades ago, so it's been a while.
Yep, the coherence is a strong point.
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 /.
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).
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.
https://www.youtube.com/watch?v=V4L8Oci_2Bs
The browser and desktop and terminal you'll inevitably want to use aren't any more part of that "complete" OS than they are on Linux (and in many ways FreeBSD Ports is more immature / less well-integrated than Linux packages).
LSU context: the completeness is out of scope.
Current aims include enhancement of the installer for FreeBSD; KDE Plasma and applications as an option.