> The proprietary software to be included takes the form of Binary Large Objects, or BLOBs. In the language of free software, this means proprietary device drivers distributed without their source code, as pure binary.
But, in https://www.debian.org/vote/2022/vote_003 , I see no mention of closed drivers (i.e., code that runs on the Debian host machine) -- only of closed firmware (i.e., code that run on the component device itself).
(Of course, though closed firmware can seem reasonable right now, it can get more complicated over time, such as by encouraging complexity to be in closed device firmware that otherwise could've been in open kernel/userland in the host. And encouraging closed firmware over open firmware. But, for now, closed firmware seems not nearly as bad for libre/open software as closed drivers and other closed software on the host. And I'll admit that I've recently specified a company standard workstation built upon Debian Stable with closed firmware blobs, pragmatically, because we needed WiFi with popular off-the-shelf laptops.)
And yes, I know it was already available, but the default installation UX matters a lot.
It is sad that they prefer to go for easy instead of keep putting pressure for companies to improve their hardware
I will put a reminder to check Debian popularity in a year's time. My bet is it will go down, most desktop people used Debian for the schizophrenic thin line they toed with Freedom Software. Otherwise any other distribution is more up to date and usable for a modern desktop/laptop, this small change will do no difference
If the project, or motivated users want to detail exactly how to run Debian without nonfree firmware, that would be great.
And just as the nonfree installer was available but kept slightly hidden (even though it's difficult to install on just about any laptop without it), I'm sure there will be Debian Developers motivated to continue providing a fully free installer for those who want it.