How I think the process for designing a hardware-driver is like

CEO: "Alright everyone, we have designed and created this great product, now let's write a driver for it!"

PM: "Great then! We just code for Windows, create an eye-catching UI but leave the actual at the worst possible case that could work!"

Dev: "B-But isn't there other OSes, like Linux and Android that people use on their computers too?"

PM: "Shut up! We are going to JUST support Windows and f*** no absolutely other OSes!

Dev: "But what if they are also developers, and want to control and use this great product by programming it themselves? We should make the driver open-source, or at least give them some APIs!"

PM: "Nonsense! They are only going to use this product on M$ Windows, and with the program we provide to them, even if it's crappy and crashes most of the time!"

Dev: "But-but..."

PM: "No buts! That's our final decision!"

And some other consumer devs are like, "F*** it, we just reverse-engineer the codes and write a new driver ourselves!"


Add Comment