JELaBarre

Authored Comments

My mistake was putting MSWin10 on a Dell all-in-one so my daughter could play Roblox as well (I should *never* enable that abomination). I've been tempted to re-configure it to only boot to Linux now, as her Google Classroom work runs just fine from there. Maybe outright wipe the MSW partition, as if it runs it wipes out the Linux EFI boot.

I can't speak to MacOS driver availability, but I have found more often than not I have better luck getting devices working with Linux out-of-the-box, while MSWin wants you hunt down vendor drivers that may or may not still be available. It's especially the case if you're using older printers and scanners, where MSWin will have broken the ABI for the only available device drivers (and the vendor has zero interest in updating them for a newer OS version). Meanwhile plug that same device into Linux, and it just works more often than not.

Your biggest problem comes from the so-called "WinPrinters" (and "WinModems" at one time). These are dependent on proprietary vendor drivers to function at all, being reliant on the OS to do all the processing that a proper peripheral should do on it's own. These are only made so the vendor can crank out cheaply-made, readily-disposable devices (which also adds to the ecological problem of electronic waste).