Oddities of linux history

I am back on io manager, working keyboard stuff, looking around at standards.

kbd utility says key boards know about back ground colors in console windows?  How and why would a key board system care about the type of window on our  display?

Then, the X server knows about keyboard maps? Why? The kernel handles keyboard io, why not go directly to linus kernel?  This is back to the 1785 introduction of the rotary press.

I need a key board lib system driven directly from the kernel io system, leave my SyncMaster 721 out of the picture, we can talk my Logitech keyboard all you want.

I see comments ike this:

 /* The x coordinate where the mouse has been pressed in the window */

Wait a minuet, my mouse in on my table, connected via USB port and disconnected from any X Y that linux knows about.

The only thing that X knows is the rate of change and direction of the mouse wheel.  It is the client who knows, and the hint to X is when the client sets the cursor, and the cursor is completely disconnected from the mouse, the client can set is anywhere.
Like the keyboard, the mouse events should be handled entirely from a kernel driver, and the client make the mapping to screen, not .  X has no justification for position except what the client set.

This kind of misdirection is a huge impediment in the industry. It masks the idea that all your character editing happens inside io manager, really; your graphic driver is completely unaware.

What really sets the click points is the editing sequence, the uer sets the rate function to the user comfort lavel. As the mouse is moved, the io manager picking up move signals will bump cause a cursor to be written to the screen at its best guess.But the rate movement is fairly accurate, the sweet stopping point fairly large, and movement reports frequent large enough that the user can guide the mouse manager.

X windows has no role in this what soever, except that it reqires reports in that it regurgitates out, IO manage need keep both mouse and keyboard out of windowing, doing the translation itself.

Then I hear reports that the mouse position in wayland is a string.  Why does wayland have a mouse pointer at all?  I thought the wayland point was to move rendering to client, and that implies the client needs to do its own io management.