Posted Dec 9, 2010 22:36 UTC (Thu) by Lestibournes (guest, #71790)
Parent article: LPC: Life after X
In order for X to successfully deal with Wayland it needs to do the following:
1. Reframe the discussion so that it's not X vs Wayland, but Wayland being a replacement for the layer of X that takes care of local display.
2. Provide a user experience on the local machine that is not noticably infirior to the experience of native Wayland apps.
3. Provide a superior experience for remote apps.
4. Provide an API that is at least as attractive to all developers as native Wayland.
For as long as X manages this, it will remain the standard API for GUIs. But the moment X falters in any one of this aspects, it can be completely gobbled up by Wayland.