Comment by rstupek
8 hours ago
They started it because the drivers people used to use from hardware vendors would routinely blue screen windows, which made MS look like the reason windows would crash. Hardware vendors are notoriously inept at software.
> They started it because the drivers people used to use from hardware vendors would routinely blue screen windows, which made MS look like the reason windows would crash. Hardware vendors are notoriously inept at software.
But hardware vendors also want Windows licenses to include with their hardware, so it's pretty easy to say "do the hardware program certification if you want the discount" and that's exactly what they did in the early days, and it worked fine. Even the peripherals (which are increasingly rare now anyway) still want to be able to put the Windows logo on their product.
At which point we still have the same question: Why are they harassing the WireGuard developers, who have their own reputation for not being inept at software and therefore shouldn't need a Microsoft certification program to assure their users that their code is trustworthy to install?
> Why are they harassing the WireGuard developers, who have their own reputation for not being inept at software
I would guess this is just large organizations Seeing Like a State whereby they "seek to force administrative legibility on their subjects by homogenizing them".
https://en.wikipedia.org/wiki/Seeing_Like_a_State
Í think their point was that Wireguard has no physical hardware, so it’s strange as a software project they’d be forced to go through verification for a hardware program.
It's a virtual network interface. So it's not really hardware, but the computer treats it like it is.
Because it's a kernel driver anyway?
Okay. So they can call it the “hardware and WireGuard” program for all I care. The reality is that MS requires this sort of approval / verification process for whatever WireGuard is doing. In true HN fashion everyone loves getting distracted by utter meaningless semantics.