> It's certainly possible to port Wayland to other operating systems, but they'll have to provide the same level of infrastructure as Linux does.
> It's certainly possible to port Wayland to other operating systems, but they'll have to provide the same level of infrastructure as Linux does.
As far as I can tell, they are not willing to add abstraction layers to accommodate other operating systems. (Or even GFX drivers that don't implement the KMS interface). If you wanted to port Wayland to BSD or OSX, you'd effectively have to implement most of the modern Linux graphics stack on them.
But I guess they'll be forced to add some layers sooner or later. Having too few of those can be just as bad as having too many.
The main thesis of Wayland is that they won't add abstraction layers. If you want to support the Wayland protocol on another os without Linux facilities, or if there is new hardware or changes in the drivers that don't fit the Wayland model, Wayland will not expand to those needs, but instead a new display server should be built to serve them.
Small projects to specifically fit the needs of the users, instead of one large one that expands to serve all badly.
For something at the bottom doesn't the opposite principal apply(not fully/all bad but to a certain extent)? Isn't this why linux is popular for so many embedded device instead of some proprietary embeded os for instance.