<?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: X characterization for MeeGo</title>
	<atom:link href="http://vignatti.com/2011/04/20/x-characterization-for-meego/feed/" rel="self" type="application/rss+xml" />
	<link>http://vignatti.com/2011/04/20/x-characterization-for-meego/</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: the damn small Wayland API &#171; Tiago Vignatti</title>
		<link>http://vignatti.com/2011/04/20/x-characterization-for-meego/#comment-2163</link>
		<dc:creator><![CDATA[the damn small Wayland API &#171; Tiago Vignatti]]></dc:creator>
		<pubDate>Wed, 17 Oct 2012 13:15:44 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=481#comment-2163</guid>
		<description><![CDATA[[...] I&#8217;ve reported about one year ago that some new systems don&#8217;t use the core X protocol and just use a few extensions instead. One would claim that this is alright cause the API would be smaller, but my opinion is if things carry on expanding outwards like they have been, we&#8217;re going get to a point where the graphics systems becomes unmaintainable. Moreover, it takes too long for the shell developer learn that just a small set of the API is needed. The X protocol flexibility feature in which developers can add many new extension as desired and the lack of a proper API deprecation mechanism is definitely a problem to consider here. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve reported about one year ago that some new systems don&#8217;t use the core X protocol and just use a few extensions instead. One would claim that this is alright cause the API would be smaller, but my opinion is if things carry on expanding outwards like they have been, we&#8217;re going get to a point where the graphics systems becomes unmaintainable. Moreover, it takes too long for the shell developer learn that just a small set of the API is needed. The X protocol flexibility feature in which developers can add many new extension as desired and the lack of a proper API deprecation mechanism is definitely a problem to consider here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vignatti</title>
		<link>http://vignatti.com/2011/04/20/x-characterization-for-meego/#comment-1959</link>
		<dc:creator><![CDATA[vignatti]]></dc:creator>
		<pubDate>Wed, 20 Apr 2011 20:21:31 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=481#comment-1959</guid>
		<description><![CDATA[thanks Sami. Chatting quickly with aberres today, he mentioned that it&#039;s being cooked the xrender removal, so it&#039;s on the way!]]></description>
		<content:encoded><![CDATA[<p>thanks Sami. Chatting quickly with aberres today, he mentioned that it&#8217;s being cooked the xrender removal, so it&#8217;s on the way!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sami</title>
		<link>http://vignatti.com/2011/04/20/x-characterization-for-meego/#comment-1958</link>
		<dc:creator><![CDATA[Sami]]></dc:creator>
		<pubDate>Wed, 20 Apr 2011 19:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://vignatti.wordpress.com/?p=481#comment-1958</guid>
		<description><![CDATA[Nice diagrams Tiago. Now let&#039;s get xrender out of there for good :)]]></description>
		<content:encoded><![CDATA[<p>Nice diagrams Tiago. Now let&#8217;s get xrender out of there for good :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
