<?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"
	>
<channel>
	<title>Comments on: Vista morning ponderings</title>
	<atom:link href="http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/feed/" rel="self" type="application/rss+xml" />
	<link>http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/</link>
	<description>Brian Pontarelli</description>
	<pubDate>Wed, 07 Jan 2009 04:43:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Brian Pontarelli</title>
		<link>http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/#comment-3179</link>
		<dc:creator>Brian Pontarelli</dc:creator>
		<pubDate>Mon, 05 Mar 2007 18:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/#comment-3179</guid>
		<description>The networking in X has severe implications for 3D rendering because what you are doing is rendering a scene on the 3D card of the XServer and then piping a bitmap across the wire. This is really just a waste of resources. The idea behind Beryl/Compiz is that there is direct communication with the GL driver that talks directly to the card. There are two ways of accomplishing this, Xgl and AIGLX. Xgl is a complete XServer that allows applications to access the graphics card directly bypassing most of the Xlib stack, including the network. AIGLX is similar but is part of Xorg and allows applications to access the graphics by going through a thin layer of Xlib code. This too eliminates the network. The reason the network just doesn't make sense in these situations is that the graphics card should spit out directly to the monitor. GPUs and modern GL graphics cards have enormous power and piping that back into main memory and then across a network essentially makes these graphics cards no better then VESA. Eventually we'll see either AIGLX or Xgl win, but the truth is that the network will never be touched in the modern Xwindows systems, making them more like a direct FB or GL device and almost nothing like an XServer. This is the only way to correctly take Linux graphics to the next logically evolutionary step.</description>
		<content:encoded><![CDATA[<p>The networking in X has severe implications for 3D rendering because what you are doing is rendering a scene on the 3D card of the XServer and then piping a bitmap across the wire. This is really just a waste of resources. The idea behind Beryl/Compiz is that there is direct communication with the GL driver that talks directly to the card. There are two ways of accomplishing this, Xgl and AIGLX. Xgl is a complete XServer that allows applications to access the graphics card directly bypassing most of the Xlib stack, including the network. AIGLX is similar but is part of Xorg and allows applications to access the graphics by going through a thin layer of Xlib code. This too eliminates the network. The reason the network just doesn&#8217;t make sense in these situations is that the graphics card should spit out directly to the monitor. GPUs and modern GL graphics cards have enormous power and piping that back into main memory and then across a network essentially makes these graphics cards no better then VESA. Eventually we&#8217;ll see either AIGLX or Xgl win, but the truth is that the network will never be touched in the modern Xwindows systems, making them more like a direct FB or GL device and almost nothing like an XServer. This is the only way to correctly take Linux graphics to the next logically evolutionary step.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keegan</title>
		<link>http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/#comment-3178</link>
		<dc:creator>Keegan</dc:creator>
		<pubDate>Mon, 05 Mar 2007 00:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/#comment-3178</guid>
		<description>Not sure I understand your comment about X; yes, it has networking capabilities, but it doesn't really add any noticable overhead whatsoever; think of those sockets connected to your own computer as just another form of interprocess communication.... 

Besides, the idea of Compiz/Beryl is that it builds on top of X and acts as a drop-in replacement for current WMs; you can't do that if you get rid of X support.</description>
		<content:encoded><![CDATA[<p>Not sure I understand your comment about X; yes, it has networking capabilities, but it doesn&#8217;t really add any noticable overhead whatsoever; think of those sockets connected to your own computer as just another form of interprocess communication&#8230;. </p>
<p>Besides, the idea of Compiz/Beryl is that it builds on top of X and acts as a drop-in replacement for current WMs; you can&#8217;t do that if you get rid of X support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Moore</title>
		<link>http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/#comment-3154</link>
		<dc:creator>Dan Moore</dc:creator>
		<pubDate>Fri, 23 Feb 2007 21:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://brian.pontarelli.com/2007/02/23/vista-morning-ponderings/#comment-3154</guid>
		<description>I simply can't believe that Vista doesn't support cygwin: http://nevali.wordpress.com/2007/01/28/cygwin-on-vista/

Cygwin is the first thing I install when I get a new Windows box, and I feel it makes developing on a windows box almost as nice as on a linux box.  

(Sure there are still linefeed issues and other inconveniences, but at least you have a valid shell.)</description>
		<content:encoded><![CDATA[<p>I simply can&#8217;t believe that Vista doesn&#8217;t support cygwin: <a href="http://nevali.wordpress.com/2007/01/28/cygwin-on-vista/" rel="nofollow">http://nevali.wordpress.com/2007/01/28/cygwin-on-vista/</a></p>
<p>Cygwin is the first thing I install when I get a new Windows box, and I feel it makes developing on a windows box almost as nice as on a linux box.  </p>
<p>(Sure there are still linefeed issues and other inconveniences, but at least you have a valid shell.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
