<?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: Native Client: An OS in Your Browser</title>
	<atom:link href="http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/</link>
	<description>Trusted Insights and Conversations on the Next Wave of Technology</description>
	<lastBuildDate>Thu, 26 Nov 2009 13:00:29 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ideal &#187; Archive du blog &#187; Native Client, la technologie RIA de Google qui risque de faire long feu</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-919289</link>
		<dc:creator>Ideal &#187; Archive du blog &#187; Native Client, la technologie RIA de Google qui risque de faire long feu</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-919289</guid>
		<description>&lt;p&gt;[...] équipes à l&#8217;origine de ce projet sont incapables de fournir une explication claire (cf.  Native Client: An OS in Your Browser). Pour faire simple, Native Client est une extension que vous installez sur votre ordinateur pour [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] équipes à l&#8217;origine de ce projet sont incapables de fournir une explication claire (cf.  Native Client: An OS in Your Browser). Pour faire simple, Native Client est une extension que vous installez sur votre ordinateur pour [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ideal &#187; Archive du blog &#187; Native Client, la technologie révolutionnaire de Google qui risque de faire long feu</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-918881</link>
		<dc:creator>Ideal &#187; Archive du blog &#187; Native Client, la technologie révolutionnaire de Google qui risque de faire long feu</dc:creator>
		<pubDate>Mon, 22 Dec 2008 09:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-918881</guid>
		<description>&lt;p&gt;[...] équipes à l&#8217;origine de ce projet sont incapables de fournir une explication clair (cf.  Native Client: An OS in Your Browser). Pour faire simple, Native Client est un&#8230; &#8220;truc&#8221; que vous installez sur votre [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] équipes à l&#8217;origine de ce projet sont incapables de fournir une explication clair (cf.  Native Client: An OS in Your Browser). Pour faire simple, Native Client est un&#8230; &#8220;truc&#8221; que vous installez sur votre [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Native Client, la technologie révolutionnaire de Google qui risque de faire long feu &#124; FredCavazza.net</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-918879</link>
		<dc:creator>Native Client, la technologie révolutionnaire de Google qui risque de faire long feu &#124; FredCavazza.net</dc:creator>
		<pubDate>Mon, 22 Dec 2008 09:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-918879</guid>
		<description>&lt;p&gt;[...] équipes à l&#8217;origine de ce projet sont incapables de fournir une explication clair (cf.  Native Client: An OS in Your Browser). Pour faire simple, Native Client est un&#8230; &#8220;truc&#8221; que vous installez sur votre [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] équipes à l&#8217;origine de ce projet sont incapables de fournir une explication clair (cf.  Native Client: An OS in Your Browser). Pour faire simple, Native Client est un&#8230; &#8220;truc&#8221; que vous installez sur votre [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Michael F. Smith Jr. Lives Here &#187; Blog Archive &#187; Blog birthing &#38; evil google&#8230;</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-918147</link>
		<dc:creator>Michael F. Smith Jr. Lives Here &#187; Blog Archive &#187; Blog birthing &#38; evil google&#8230;</dc:creator>
		<pubDate>Tue, 16 Dec 2008 11:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-918147</guid>
		<description>&lt;p&gt;[...] about what is happening in the net space in regards to browsers and native clients. Here is another post from GigaOm about the native client with some quotes from the google team: Another thing the Google staffers [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] about what is happening in the net space in regards to browsers and native clients. Here is another post from GigaOm about the native client with some quotes from the google team: Another thing the Google staffers [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-918029</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Mon, 15 Dec 2008 19:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-918029</guid>
		<description>&lt;p&gt;Known internally as &quot;Sulu&#039;s Ear&quot; the ultimate  placement engine for ad sense.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Known internally as &#8220;Sulu&#8217;s Ear&#8221; the ultimate  placement engine for ad sense.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: gp</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-917930</link>
		<dc:creator>gp</dc:creator>
		<pubDate>Mon, 15 Dec 2008 04:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-917930</guid>
		<description>&lt;p&gt;and how its different from mozilla xul runner https://developer.mozilla.org/en/XULRunner ?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>and how its different from mozilla xul runner <a href="https://developer.mozilla.org/en/XULRunner" rel="nofollow">https://developer.mozilla.org/en/XULRunner</a> ?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: james</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-917882</link>
		<dc:creator>james</dc:creator>
		<pubDate>Sun, 14 Dec 2008 19:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-917882</guid>
		<description>&lt;p&gt;So let me get this straight, web OS = OS inside of a browser which is inside of an OS? Brilliant.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>So let me get this straight, web OS = OS inside of a browser which is inside of an OS? Brilliant.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: ronald</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-917876</link>
		<dc:creator>ronald</dc:creator>
		<pubDate>Sun, 14 Dec 2008 18:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-917876</guid>
		<description>&lt;p&gt;Do I miss something, or where is the magical thing that makes it so secure.
Machine security is a matter of handling uncertainty, you can either limit it by limiting functionality (really globally restrictive sandbox ) or you try to force it  to allow local applications only to do certain things(SeLinux).   Both models will break (SeLinux later, since it deals with more specifics, but a pain to get right) , because there is always the creativity of the human brain to introduce the unknown at a later time.  So what&#039;s Google&#039;s silver bullet and why is it so much better then everybody else.
Also don&#039;t you have to deal with at least three latencies, Sever application and load, Network and local. Fixing one, nice, but no cigar, specially  my machine lately always waits for some ad network, one is owned by Google.  Which leads one to believe the business model needs some fixing too.&lt;/p&gt;

&lt;p&gt;On the other hand if a research Engineer can not explain in clear abstracts what he is building,you will end up in a mess if you put that system in production and have it maintained for a while. Since there is no clear guideline of what is what and why it&#039;s there.
A few questions that come to mind:
What&#039;s their definition of an OS?
If it&#039;s an OS, they run an OS-App-OS or a VM-(OS-APP-OS)*n why? Where is the advantage of that convoluted setup for the user. 
They already have fault separation in Chrome don&#039;t they? How many times do they have to do that?
What&#039;s their goal, it&#039;s called research for a reason, and not re-guided for the same reason.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Do I miss something, or where is the magical thing that makes it so secure.
Machine security is a matter of handling uncertainty, you can either limit it by limiting functionality (really globally restrictive sandbox ) or you try to force it  to allow local applications only to do certain things(SeLinux).   Both models will break (SeLinux later, since it deals with more specifics, but a pain to get right) , because there is always the creativity of the human brain to introduce the unknown at a later time.  So what&#8217;s Google&#8217;s silver bullet and why is it so much better then everybody else.
Also don&#8217;t you have to deal with at least three latencies, Sever application and load, Network and local. Fixing one, nice, but no cigar, specially  my machine lately always waits for some ad network, one is owned by Google.  Which leads one to believe the business model needs some fixing too.</p>

<p>On the other hand if a research Engineer can not explain in clear abstracts what he is building,you will end up in a mess if you put that system in production and have it maintained for a while. Since there is no clear guideline of what is what and why it&#8217;s there.
A few questions that come to mind:
What&#8217;s their definition of an OS?
If it&#8217;s an OS, they run an OS-App-OS or a VM-(OS-APP-OS)*n why? Where is the advantage of that convoluted setup for the user. 
They already have fault separation in Chrome don&#8217;t they? How many times do they have to do that?
What&#8217;s their goal, it&#8217;s called research for a reason, and not re-guided for the same reason.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-917845</link>
		<dc:creator>anonymous</dc:creator>
		<pubDate>Sun, 14 Dec 2008 05:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-917845</guid>
		<description>&lt;p&gt;Looks more like Inferno plugin http://www.vitanuova.com/inferno/plugin/index.html&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Looks more like Inferno plugin <a href="http://www.vitanuova.com/inferno/plugin/index.html" rel="nofollow">http://www.vitanuova.com/inferno/plugin/index.html</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mathew Ingram</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-917817</link>
		<dc:creator>Mathew Ingram</dc:creator>
		<pubDate>Sat, 13 Dec 2008 21:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-917817</guid>
		<description>&lt;p&gt;Thanks, Jerry :-)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks, Jerry :-)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry</title>
		<link>http://gigaom.com/2008/12/13/native-client-an-os-in-your-browser/#comment-917804</link>
		<dc:creator>Jerry</dc:creator>
		<pubDate>Sat, 13 Dec 2008 18:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=32041#comment-917804</guid>
		<description>&lt;p&gt;You must be doing something right to get three Google engineers on the phone!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You must be doing something right to get three Google engineers on the phone!</p>]]></content:encoded>
	</item>
</channel>
</rss>
