▲ | baq 6 days ago | |||||||
Hardware is so broken that getting useful functionality basically amounts to casting magic spells and drivers are supposed to be master wizards who know all the points where the spell book is wrong or incomplete. If you think drivers are bad, don’t look at the hardware, you’ll get depressed. | ||||||||
▲ | sitkack 6 days ago | parent [-] | |||||||
This is fundamentally the problem. Just like being able to send OTA updates has enshittified all software, having this magic shim layer that fixes hardware problems has enabled shit hardware, and then foisted all this complexity into the OS. Many abstractions are like bondo, they just cover rot. I am addressing your comment and eru's question about drivers. The hardware that would normally need drivers should present itself over a fixed, well documented protocol. Think virtio, or usb device classes but more comprehensive. This would also allow for said hardware to rigorously tested before it ever sees an OS. As it is now, because the hardware is shit and requires a driver, you can't really test the hardware in a way that an OS would expect because it requires the OS driver to even start to function. The job of the OS is now to repair broken hardware. https://docs.oasis-open.org/virtio/virtio/v1.3/virtio-v1.3.h... https://en.wikipedia.org/wiki/USB_communications_device_clas... (the only good thing to come out of usb) | ||||||||
|