Bad NIH, good NIH
Posted Mar 8, 2013 19:24 UTC (Fri) by HelloWorld
In reply to: Bad NIH, good NIH
Parent article: Canonical reveals plans to launch Mir display server (The H)
I still think that a display protocol was a very important innovation and that making drawing direct to the framebuffer the core operation is a huge step back.
I don't see why. Afaics, there were essentially two reasons for putting the rendering code in the X server:
- to stop a client from messing with another client's pixmaps etc.
- to clip window contents
- to share the rendering code between multiple clients to save memory
None of these apply any longer. The kernel does graphics memory management, everything is composited and we have shared libraries (those didn't exist back when X was conceived). Otoh, client-side rendering is faster because it avoids the protocol overhead, it's more flexible because the server doesn't have to be changed in order to provide new drawing operations, and if you really want a remove rendering protocol, it can be done on top of wayland. I think that not putting rendering in the protocol is the right thing to do.
to post comments)