Because they don't want ignorant end users to blame them if the ancient, unpatched version of GRUB that's at issue is used as part of an exploit attacking Windows boxes.
I wonder if there's a Gentoo binpkg host for i486 specifically, since it might almost be practical then. (Or you could set up your own.)
Also out of the loop, but my guess is that Wayland hasn't defined a specific API for the purpose yet, and their security model doesn't allow programs to see the content of other programs' windows. X11 doesn't attempt to keep programs from seeing what other programs put on screen, so no specific API is needed there.
Actually, if you check deep down in the list of installables, you'll find that Gentoo still supports the even less capable i486 variant. A laptop from 2010 is positively a spring chicken compared to some of the things it can be made to run on. Itanium is only being desupported because it's being dropped upstream by the kernel and other chunks of the toolchain (and the only actual hardware they had to test on died a while ago).
date
is the command for setting the system date and time from the command line. Nothing to do with formatting, beyond the fact that it presumably applies system locale settings when echoing date-time info.
I only need it for the very occasional testing of open-source software on Windows, using the precanned VM images provided by Microsoft (last I checked, they had none for qemu, or I would be using that instead). And if you're using software commercially, you'd better be damned sure you understand the licensing before setting up. A company of any size will have lawyers vetting that anyway.
In other words, I don't disagree with you, but those issues don't matter for my use case.
Raw qemu at the command line for the one I use on a daily basis (not recommended for the average user). VirtualBox if I need to spin something up quickly but don't expect to need to keep it past the current testing cycle.
ext4 on all hard disks, but my installs are all several years old at this point, and I might choose differently if I were starting over from scratch. The boot partition on the ancient laptop might actually be ext2; I don't remember and it's certainly old enough that that might still have been preferred Gentoo procedure when I first set it up. Removable media might be ext3, ext4, or vfat, depending on compatibility needs and how long ago I formatted it. If I buy an SD card or USB stick that turns out to be preformatted in exFAT, I reformat it before use to ensure everything can read it.
They're all solidly reliable filesystems (well, except for the vfat), but perhaps not the most featureful.
In the general case, no, but there are some rare specific cases where that does work.
If you're trying to produce Linux media that will boot on a single-board computer that has an onboard bootloader, like a Pi 4, you can indeed just partition the target medium and copy the files manually (been there, done that, working with a custom Gentoo install with no ISO).
If the bootloader has to be on the target medium (as it would for a desktop or laptop), then that won't work unless you also do a manual bootloader install after copying everything. Not impossible, but at that point you're hitting the level of complexity where it's easier to figure out the correct dd
command.
(As for Windows? Don't even bother. It hates being worked on with anything but its own tools.)
Well, you're not affected by this specific bug, anyway. Whether you're virtuous in other aspects of your life is beyond the knowledge of anyone here. 😜
@nyan
@sh.itjust.works