Types of Drivers

Every driver shares the same essential job — translate requests, carry answers, hide complexity — but the demands of that job change enormously depending on what is being served. A part that stores precious data worries above all about never losing it, while a part that paints the screen worries about finishing each frame in time.

This is why there are families of drivers rather than a single universal one. Each family is the same core idea tuned to a particular kind of work, shaped by what matters most for the component it serves.

These distinctions are not merely technical curiosities. They explain why a slow connection and a stuttering display feel like different kinds of problems, and why fixing one rarely fixes the other. Each family has its own priorities, its own ways of failing, and its own ways of recovering.

Seeing the families side by side makes the whole landscape feel navigable. Instead of a confusing pile of components, you begin to recognise patterns: this part behaves like that one, this trouble resembles that trouble, and the right way to think about each becomes clearer.