5 ms·

Negative. Backlighting is vendor specific. Different implementations offer different configurations. I do agree you probably want a base object for inheritan

Negative. Backlighting is vendor specific. Different implementations offer different configurations. I do agree you probably want a base object for inheritance, exposing a common interface wouldn't be a good idea. No matter what, you need to implement your abstraction. You're always going to end up with a list of vendor specific implementations.

cnst 7y ago
> Negative. Backlighting is vendor specific. Different implementations offer different configurations. Are you joking? For an analogy, do any NIC vendors even provide their own tools for configuring their Ethernet cards? And even if some do, how many people actually bother to use those, instead of OS-specific utilities like ifconfig? How's backlighting any different here?
- regularfry 7y ago
  The networking analogy would be things like DPDK, where yes, you do need to know what the hardware is doing, and yes, there's vendor-specific support. The answer to "how many people bother" would be "as many as have a damn good reason to do so." http://doc.dpdk.org/guides/nics/overview.html http://doc.dpdk.org/guides/nics/overview.html shows the non-homogeneity of NIC feature support across vendors; if you don't care about this stuff, there's no reason to know it, but if you do, it's make or break.
  - cnst 7y ago
    Sure, that's a lot of variation. Sure, some of these features are essential for certain applications, like checksum offload etc. However, most of these features are still uniform enough that a whole bunch of them are supported by standard drivers included with all BSD operating systems, and configurable with the standard ifconfig of each BSD, too: http://mdoc.su/-/ifconfig.8 http://mdoc.su/-/ifconfig.8 The fact that you even have a whole table with these features shows that these features are not that difficult to categorise and unbrand to be general enough to have OS-defined behaviours and configurations for.

cnst 7y ago

> Negative. Backlighting is vendor specific. Different implementations offer different configurations. Are you joking? For an analogy, do any NIC vendors even provide their own tools for configuring their Ethernet cards? And even if some do, how many people actually bother to use those, instead of OS-specific utilities like ifconfig? How's backlighting any different here?

regularfry 7y ago
The networking analogy would be things like DPDK, where yes, you do need to know what the hardware is doing, and yes, there's vendor-specific support. The answer to "how many people bother" would be "as many as have a damn good reason to do so." http://doc.dpdk.org/guides/nics/overview.html http://doc.dpdk.org/guides/nics/overview.html shows the non-homogeneity of NIC feature support across vendors; if you don't care about this stuff, there's no reason to know it, but if you do, it's make or break.
- cnst 7y ago
  Sure, that's a lot of variation. Sure, some of these features are essential for certain applications, like checksum offload etc. However, most of these features are still uniform enough that a whole bunch of them are supported by standard drivers included with all BSD operating systems, and configurable with the standard ifconfig of each BSD, too: http://mdoc.su/-/ifconfig.8 http://mdoc.su/-/ifconfig.8 The fact that you even have a whole table with these features shows that these features are not that difficult to categorise and unbrand to be general enough to have OS-defined behaviours and configurations for.