The linux xwindows foul up

Gamers discovered it first, that is why we have special game machines, these games separate io from windows, and both MS and linux fouled this up.

And that is why my serial mouse has discontinued support, the linux architect knew that ultimately the io would have to be separated from the graphics driver.  It was some kind of secret, most software developers worked around it.  Combining the two functions has slowed the development  of linux and MS windows.

The industry is headed toward a single unified management of both keyboard and mouse separate from graphics.  Now we have some dufas in small town USA having to fix the problem, how weird is that?

The bug is tied to Moore's Law, the original design needed to be compact, and hey violated the rules, creating a semantic loop in the design that has fooled the user for years.  But, I am not the only one looking at using 64 bit address space to partition functions and make them reconfigurable.  QT must have the problem when they support both gamers and regular users. I am almost certain I have run up against an embarrassing design bug, but it is now easy to fix. The calculation on mouse position is strictly an IO function.. The keyboard mapping is a lot simpler if Xwindows is not trying to redefine characters or managing scan codes.

The problem is easy to fix now because the xcb, QT, and X folks have prepped the path forward.  Now is the time for wayland to dump the mouse and keyboard function onto a separate IO manager. The graphics driver is completely unaware that the user is watching the cursor and guiding IO.  The graphics driver is also completely unaware that some gamer is trying to shoot down an object on the screen.  Graphics knows nothing about any of this stuff.

I should be able to take Windows10, basic core and io; load that onto one of the game machines and it should work fine. The high speed iO should be adaptable to a variety of USB devices, unknown to the windowing system.  The windowing system should have allowed DirectX access to the frame buffer from the beginning, except it was hard to do with mouse and keyboard control packed into graphics.