Comment Re: a path-traversal attack (Score 2) 78
No driver needed?
You're not understanding the incentive structure that led to this state of affairs in the first place. To use USB would mean that they would have to do a ton of driver work. They would have to implement these generic control surfaces and they would have to ensure that their hardware does what the USB specs say it should. You'd end up with a USB RGB controller chip.
If you haven't noticed, RGB controller chips are a lot more electronically simple than that. They are small-project simple I/O-programmed chips running on simple control buses clearly designed and implemented in a hardware world of Arduinos and Raspis, GPIO buses, I2C, the old stuff. If you were around in the 1990s, you would recognize this immediately for what it is: the way things were done before NT, when DOS and Windows software frequently shoved the OS aside and ran on bare metal. In the late 90s as NT crept toward the home PC world, the impending loss of direct hardware access was one of the obvious compatibility issues visible on the horizon with the NT world-to-come, and the begrudging acceptance that this stuff was all "legacy" and we'll all have to drive our hardware like grownups in the future began.
The issue with this is simply one of cost and complexity. Smaller hardware projects will not be able to afford such overhead. Implementing an RGB controller you're driving directly from your shitty gamer system tray app is a lot more straightforward than properly implementing every layer of a universal device stack. No one ever bothered to do things the "right way" because it was never a pressing issue.