The Wayland Situation: Facts About X vs. Wayland (Phoronix)

Posted Jun 9, 2013 21:08 UTC (Sun) by Cyberax (✭ supporter ✭, #52523)
In reply to: The Wayland Situation: Facts About X vs. Wayland (Phoronix) by dig
Parent article: The Wayland Situation: Facts About X vs. Wayland (Phoronix)

X on Wayland is easy. You just run a rootless server with a Wayland backend. Exactly as you would do it on Windows and Mac OS.

(Log in to post comments)

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

Posted Jun 11, 2013 8:28 UTC (Tue) by mmarq (guest, #2332) [Link]

So what is the point of Wayland ?

IF a dev codes for X, and he continues, wouldn't be much better to run it directly on X instead of a server on top of another ?

And yes i read all the arguments, but i see 2 trends developing for applications. One is Kronos the other is HSA, and they are some how very close related in many points.

Even Nvidia will eventually join(both) with their ARM push, and the same with Apple(LLVM is the dev base of HSA and Apple is LLVM). More dubious is Intel and Microsoft. The strength of X is not what lays ahead but the enormous baggage that lays behind... Why change ?... in a pure app POV what isn't broke don't fix it, the DS is *orthogonal*... so again why change ?

Is any of those DS , X, Wayland or Mir, going in the direction of the industry ?

(if i was an app dev right now, i would want it on Mac, Linux, Android and Windows etc... if possible... all this discussions and promises don't give me any incentive)

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

Posted Jun 11, 2013 17:18 UTC (Tue) by Tobu (subscriber, #24111) [Link]

Devs code for toolkits: SDL, Gtk, Qt, or even more high-level. One of the toolkits' jobs is to provide portability (though apps will use platform calls when the toolkits are weak on that front). I don't think a brand-new Kronos standard will displace them.