<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: the damn small Wayland API</title>
	<atom:link href="http://vignatti.com/2012/10/17/the-damn-small-wayland-api/feed/" rel="self" type="application/rss+xml" />
	<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/</link>
	<description>my blog</description>
	<lastBuildDate>Tue, 26 Mar 2013 06:44:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Rune K. Svendsen</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2700</link>
		<dc:creator><![CDATA[Rune K. Svendsen]]></dc:creator>
		<pubDate>Tue, 26 Feb 2013 09:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2700</guid>
		<description><![CDATA[That&#039;s not quite true. Any program that uses Xlib calls will not work with Wayland (or the part that depends on the call will not work). I&#039;m not sure how many apps do this, but I wouldn&#039;t be surprised if it is fairly common (at least among graphics apps), which isn&#039;t really surprising given that no serious substitute for X has existed for about 30 years.]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s not quite true. Any program that uses Xlib calls will not work with Wayland (or the part that depends on the call will not work). I&#8217;m not sure how many apps do this, but I wouldn&#8217;t be surprised if it is fairly common (at least among graphics apps), which isn&#8217;t really surprising given that no serious substitute for X has existed for about 30 years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: X.Org est mort, vive Wayland! &#124; Club Linux Atomic</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2693</link>
		<dc:creator><![CDATA[X.Org est mort, vive Wayland! &#124; Club Linux Atomic]]></dc:creator>
		<pubDate>Fri, 21 Dec 2012 15:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2693</guid>
		<description><![CDATA[[...] une petite idée de leurs différences, l’interface de programmation (API) de Wayland est environ 15 fois plus petite que celle de [...]]]></description>
		<content:encoded><![CDATA[<p>[...] une petite idée de leurs différences, l’interface de programmation (API) de Wayland est environ 15 fois plus petite que celle de [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: X.Org est mort, vive Wayland! &#124; Geek-City Blog</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2692</link>
		<dc:creator><![CDATA[X.Org est mort, vive Wayland! &#124; Geek-City Blog]]></dc:creator>
		<pubDate>Mon, 17 Dec 2012 21:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2692</guid>
		<description><![CDATA[[...] une petite idée de leurs différences, l’interface de programmation (API) de Wayland est environ 15 fois plus petite que celle de [...]]]></description>
		<content:encoded><![CDATA[<p>[...] une petite idée de leurs différences, l’interface de programmation (API) de Wayland est environ 15 fois plus petite que celle de [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergio Costas</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2197</link>
		<dc:creator><![CDATA[Sergio Costas]]></dc:creator>
		<pubDate>Sat, 20 Oct 2012 20:23:34 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2197</guid>
		<description><![CDATA[The interesting point is that, currently, nearly nobody works with X directly, but always relies on libraries like GTK and Qt. By porting both to Wayland (which, in fact, already has been done), all programs based on them will work both in X and in Wayland. So the compatibility layer will be needed only for old programs, like the ones based on Motif/Lesstif or similar. How many programs do you use that work with Motif?]]></description>
		<content:encoded><![CDATA[<p>The interesting point is that, currently, nearly nobody works with X directly, but always relies on libraries like GTK and Qt. By porting both to Wayland (which, in fact, already has been done), all programs based on them will work both in X and in Wayland. So the compatibility layer will be needed only for old programs, like the ones based on Motif/Lesstif or similar. How many programs do you use that work with Motif?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CSRedRat</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2196</link>
		<dc:creator><![CDATA[CSRedRat]]></dc:creator>
		<pubDate>Sat, 20 Oct 2012 19:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2196</guid>
		<description><![CDATA[XWayland in X.Org Server 1.14!]]></description>
		<content:encoded><![CDATA[<p>XWayland in X.Org Server 1.14!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2180</link>
		<dc:creator><![CDATA[Martin]]></dc:creator>
		<pubDate>Thu, 18 Oct 2012 16:36:44 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2180</guid>
		<description><![CDATA[@Nick:
Sorry, having to install an X server (or some X extension to Wayland) to get compatibility is as good as it is when using Windows or Mac. It sucks. Also, if you have it always installed by default, the API which has to be supported is now X + Wayland. So what is the point? 
But there is also the other way round, Wayland clients will not work on X. (Well the toolkit could forever support both, but what is the point then?) This breaks the ecosystem. And for what reason? On the Wayland homepage it says that everyhing could also have been accomplished as an extension to X. 

See, I really like small, nice, and elegant interfaces. But if I think of how Wayland fits in the overall picture, I only see how it makes things less functional and more complicated. e.g. have an extra X app for backwards compatiblity, which will probably bit rot soon. Having toolkits have more backends... Having later some kind of network transparency added back in as a kludge, because people realize that it is useful in a world where there is fast internet everywhere (which is then not fully functional, because it &quot;just moves pixels&quot; and does not offer full integration) 

Wayland is only small, simple, and elegant if you ignore all this.

@Kaacz: 
Imagine having devices (mobile, TV, wlan router, fridge, ...) which instead of having stupid web interfaces could have programs with a nice GUI which you can show on your laptop. One could cut&amp;paste a number from the adress book or drag&amp;drop a movie to the TV or just move the window of the TV player from the mobile to the TV when coming home and a lot more. I cannot think how one can design a display system without network transparency at its core in 2012. Probably Apple has to do it at some point before people realize how cool this is.]]></description>
		<content:encoded><![CDATA[<p>@Nick:<br />
Sorry, having to install an X server (or some X extension to Wayland) to get compatibility is as good as it is when using Windows or Mac. It sucks. Also, if you have it always installed by default, the API which has to be supported is now X + Wayland. So what is the point?<br />
But there is also the other way round, Wayland clients will not work on X. (Well the toolkit could forever support both, but what is the point then?) This breaks the ecosystem. And for what reason? On the Wayland homepage it says that everyhing could also have been accomplished as an extension to X. </p>
<p>See, I really like small, nice, and elegant interfaces. But if I think of how Wayland fits in the overall picture, I only see how it makes things less functional and more complicated. e.g. have an extra X app for backwards compatiblity, which will probably bit rot soon. Having toolkits have more backends&#8230; Having later some kind of network transparency added back in as a kludge, because people realize that it is useful in a world where there is fast internet everywhere (which is then not fully functional, because it &#8220;just moves pixels&#8221; and does not offer full integration) </p>
<p>Wayland is only small, simple, and elegant if you ignore all this.</p>
<p>@Kaacz:<br />
Imagine having devices (mobile, TV, wlan router, fridge, &#8230;) which instead of having stupid web interfaces could have programs with a nice GUI which you can show on your laptop. One could cut&amp;paste a number from the adress book or drag&amp;drop a movie to the TV or just move the window of the TV player from the mobile to the TV when coming home and a lot more. I cannot think how one can design a display system without network transparency at its core in 2012. Probably Apple has to do it at some point before people realize how cool this is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaacz</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2179</link>
		<dc:creator><![CDATA[Kaacz]]></dc:creator>
		<pubDate>Thu, 18 Oct 2012 13:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2179</guid>
		<description><![CDATA[@Martin &gt; network transparency which is actually a very cool feature especially for mobile devices. &lt;

Really ? 95% users of mobile devices don&#039;t need get mobile &quot;desktop&quot; to other device. Yes, maybe need get other desktop on mobile device client. But this no make problem with use Wayland on mobile device. Simply install x-app expansion running on top Wayland.]]></description>
		<content:encoded><![CDATA[<p>@Martin &gt; network transparency which is actually a very cool feature especially for mobile devices. &lt;</p>
<p>Really ? 95% users of mobile devices don&#039;t need get mobile &quot;desktop&quot; to other device. Yes, maybe need get other desktop on mobile device client. But this no make problem with use Wayland on mobile device. Simply install x-app expansion running on top Wayland.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2177</link>
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Thu, 18 Oct 2012 11:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2177</guid>
		<description><![CDATA[Look, nobody is forced to used Wayland. X is not going anywhere, and they can actually coexist nicely.

So even if everyone everywhere was using wayland, X can stick around for as long as backward compatibility is a desired feature.

Also, Wayland does not prohibit network transparency.]]></description>
		<content:encoded><![CDATA[<p>Look, nobody is forced to used Wayland. X is not going anywhere, and they can actually coexist nicely.</p>
<p>So even if everyone everywhere was using wayland, X can stick around for as long as backward compatibility is a desired feature.</p>
<p>Also, Wayland does not prohibit network transparency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2176</link>
		<dc:creator><![CDATA[Martin]]></dc:creator>
		<pubDate>Thu, 18 Oct 2012 06:25:34 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2176</guid>
		<description><![CDATA[So what? X ran fine with 4 MB or so. I am much more concerned about loosing forward compatibility for stuff that has worked for decades. And network transparency which is actually a very cool feature especially for mobile devices.]]></description>
		<content:encoded><![CDATA[<p>So what? X ran fine with 4 MB or so. I am much more concerned about loosing forward compatibility for stuff that has worked for decades. And network transparency which is actually a very cool feature especially for mobile devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Herpner</title>
		<link>http://vignatti.com/2012/10/17/the-damn-small-wayland-api/#comment-2174</link>
		<dc:creator><![CDATA[Herpner]]></dc:creator>
		<pubDate>Thu, 18 Oct 2012 03:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=576#comment-2174</guid>
		<description><![CDATA[Needs more cowbell, clearly.]]></description>
		<content:encoded><![CDATA[<p>Needs more cowbell, clearly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
