If all you got is ~30 carefully picked packages to create a fully custom ISS installation
With 30 packages, what you've got is a toy, perhaps a single-purpose embedded installation, not a useful OS; and IMO the knowledge required to curate such minimalism has a high cost. I spend far more time updating a ~40G Linux installation than I do Windows - Ubuntu's package manager accosts me at least once a week. At least the pestering for reboots is a lot easier to ignore - I have a script in a loop on Windows, after once losing work to an ill-timed reboot prompt stealing focus.
EFI BIOS is know for a slightly worse performance for linux vs windows
No shit. I wasted a whole day - last Friday, to be exact - figuring out how to get Ubuntu 12.04.2 LTS working on a modern UEFI machine with full disk encryption and Nvidia graphics card. UEFI doesn't supply old BIOS text routines, and Ubuntu GRUB2 defaults don't work, such that when you switch from nouveau's hilariously unstable drivers (hard X.Org crash if you move windows too quickly) to nvidia-current you don't get a prompt at boot-up to enter your password - just a black screen of apparent death. You have to configure a framebuffer that works with the Nvidia card and live with NVRM's kernel log warnings about only supporting VGA text consoles.
Most of all I really resent Ubuntu forcing me to learn how all these pieces are put together, so I could fix it. Using it as a desktop OS daily, I remain more convinced than ever that it is best put to work via an ssh session in a different OS. The command-line is the only UI on it that reliably works.
> Most of all I really resent Ubuntu forcing me to learn how all these pieces are put together, so I could fix it. Using it as a desktop OS daily, I remain more convinced than ever that it is best put to work via an ssh session in a different OS. The command-line is the only UI on it that reliably works.
Why is it Canonicals fault Microsoft paid off (not exclusively, I know at Intel was also involved) and pushed for UEFI on all modern motherboards? Bios was working fine for a decade with Linux, UEFI has been terrible because there have been efforts in its adoption to only target Windows and obfuscate or just outright not support other OSes on some boards.
Your experience doesnt really apply to how production systems are managed. And 30 packages is enough and is useful. Production systems dont update themselves just because theres a new package in the repo, thats what people regular users do.
In production systems updates are rolled out only if there is a must have benefit, or a serious security patch.
I dont really get your point if you dont like linux then dont use it, its pretty easy to manage.
With 30 packages, what you've got is a toy, perhaps a single-purpose embedded installation, not a useful OS; and IMO the knowledge required to curate such minimalism has a high cost. I spend far more time updating a ~40G Linux installation than I do Windows - Ubuntu's package manager accosts me at least once a week. At least the pestering for reboots is a lot easier to ignore - I have a script in a loop on Windows, after once losing work to an ill-timed reboot prompt stealing focus.
EFI BIOS is know for a slightly worse performance for linux vs windows
No shit. I wasted a whole day - last Friday, to be exact - figuring out how to get Ubuntu 12.04.2 LTS working on a modern UEFI machine with full disk encryption and Nvidia graphics card. UEFI doesn't supply old BIOS text routines, and Ubuntu GRUB2 defaults don't work, such that when you switch from nouveau's hilariously unstable drivers (hard X.Org crash if you move windows too quickly) to nvidia-current you don't get a prompt at boot-up to enter your password - just a black screen of apparent death. You have to configure a framebuffer that works with the Nvidia card and live with NVRM's kernel log warnings about only supporting VGA text consoles.
Most of all I really resent Ubuntu forcing me to learn how all these pieces are put together, so I could fix it. Using it as a desktop OS daily, I remain more convinced than ever that it is best put to work via an ssh session in a different OS. The command-line is the only UI on it that reliably works.