3 ms·
I think an X12 would be amazing. Incorporate some features from the open-source version of NoMachine NX to make network transparency work better over the intern
by wkat4242 3y ago
I think an X12 would be amazing. Incorporate some features from the open-source version of NoMachine NX to make network transparency work better over the internet with high latency. Incorporate some better security mechanisms.
With the world moving ever more again towards distributed computing (Like Windows desktop in the cloud which you can rent now from Microsoft) it would be amazing if each window on my computer could run on a different physical computer. I could run my 3D Design program on a heavy instance somewhere, my browser on a medium instance (and sandboxed), and some smaller programs locally. X11 can do all that today (and it could in 1995!) but it's not very good at it due to the latency sensitivity introduced by the many roundtrips in the protocol. Wayland can't because it's really designed to be fully local.
- vidarh 3y agoI'm halfway tempted given I've replaced almost all of my stack with my own code barring the browser and X. I think, if I was going to consider and "X12" though, what I think would be the steps to start with would to trim the starting point down aggressively, to reduce the maintenance burden: * "Promote" certain extensions, like BigRequests and XRender and enable them automatically. * XRender requires a fixed set of visuals, including 24 bit and 32 bit. As a result, if you require XRender you can reasonably aggressively deprecate most inferior visuals. You might lose some old software without shims/a proxy that way. But frankly I don't think it's worth caring enough - if any of it is worth keeping, a shim is fine. * Aggressively deprecate most legacy rendering calls and options. Almost all of it can trivially be shimmed client side or supported via a proxy if any extant/in use apps still support them. This includes support for server-side bitmap fonts (they can trivially be supported by XRender glyph support). * Remove most backends. Support maybe one "dumb"/basic backend for legacy use, but remove as much possible. The point is you can do a vastly better job if you strip the thing bare first.