The millions of lines of code aren't inherent to the problem. Here's the 9front ACPI interpreter: http://git.9front.org/plan9front/plan9front/HEAD/sys/src/lib

The millions of lines of code aren't inherent to the problem. Here's the 9front ACPI interpreter: http://git.9front.org/plan9front/plan9front/HEAD/sys/src/libaml/f.html http://git.9front.org/plan9front/plan9front/HEAD/sys/src/lib... And the USB stack, user and kernel side: http://git.9front.org/plan9front/plan9front/HEAD/sys/src/cmd/nusb/lib/f.html http://git.9front.org/plan9front/plan9front/HEAD/sys/src/cmd... http://git.9front.org/plan9front/plan9front/HEAD/sys/src/9/port/devusb.c/f.html http://git.9front.org/plan9front/plan9front/HEAD/sys/src/9/p... http://git.9front.org/plan9front/plan9front/HEAD/sys/src/9/port/usbxhci.c/f.html http://git.9front.org/plan9front/plan9front/HEAD/sys/src/9/p... Even the complex drivers, like wifi, are relatively small: http://git.9front.org/plan9front/plan9front/HEAD/sys/src/9/pc/etheriwl.c/f.html http://git.9front.org/plan9front/plan9front/HEAD/sys/src/9/p... Linux code is unpleasant. I don't want to deal with it. Give me clear, well-written docs instead. Of course, since that never happens, we just end up reading the linux code and reimplementing it in a way that's acceptably clean.