Hacker News Reader

If I understand correctly, it just wraps an existing Linux driver in a container. You can hardly call that writing a driver.

Would calling it a "driver adapter" fit more accurately .. ?

I don't think so, no. It does not appear to be functioning as an OSX device driver. It's just hosting a network print server in docker.

Tbh I actually like this even more than writing a driver …

Makes it so if there’s an issue I don’t get a kernel panic

Maybe it could write something CUPS compliant though ?

To be fair print drivers have mostly been user mode. On Windows since win2000, and on macOS - since macOS 10 Cheetah.

Why not call it a containerized driver?