H. William Welliver III wrote:
Though, also keep in mind that not everyone is going to be able to use libusb, so while I don't advocate over-classifying things, it might be somewhat ill-considered to use a generic (USB) name for something that's actually quite implementation specific, unless you were also planning on offering a generic interface to multiple USB-IO backends. Consider this
I briefly checked, and as far as I can see, libusb-1.0 is the *only* usb library/interface being offered which is cross-OS. This does not mean that in the future, something else might arise which offers the same, but I'd consider it extremely unlikely. So, we could name it libUSB or similar, but for brevity, USB sounded better.
case-in-point: file event notification apis are generally OS-specific, so we have System.Inotify and (soon) System.FSEvents which will hopefully plug into a more universal interface that works no matter what OS you're running.
AFAICS, libusb is actively being ported and/or offered on several OSes. But if you know of competing offerings and/or know that libusb has shortcomings which make it likely that some would not want to use it, please speak up.