2 ms·
I don't mean to be harsh, but if there's a codepath that is exercised on your hardware, but not on mine, I don't think it would be fair for me to deem it as "bl
by dormento 4mo ago
I don't mean to be harsh, but if there's a codepath that is exercised on your hardware, but not on mine, I don't think it would be fair for me to deem it as "bloat". There are a TON of supported devices and use cases that are not my own, but are essential to someone else.
- WD-42 4mo agoIf you are still using ISDN you could maintain a fork. This is one of the main examples of drivers that were removed.
- asgraham 4mo agoSure, sure. I’m not arguing for removing drivers for uncommon devices, or even rare devices. But there’s a line somewhere. Maybe it’s at “devices that no longer exist.” But I think it’s somewhere before that. And I have no idea how you’d figure out which devices fall where around this hypothetical line. I can only hope that they had good justification for these removals.
- franktankbank 4mo agoMaybe that points to an architecture issue? Is kernel driver support general enough to support all hardware in theory? If so it should be on hardware to provide a compatible api IMO. Note: I really have no experience in any of this there is probably more important things to consider like security/control or something.