<?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: Et&#8217;Tube Brutus? Or Ajax ..</title>
	<atom:link href="http://devdawn.com/2006/08/14/ettube-brutus-or-ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://devdawn.com/2006/08/14/ettube-brutus-or-ajax/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 05:23:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Adam</title>
		<link>http://devdawn.com/2006/08/14/ettube-brutus-or-ajax/#comment-3021</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 14 Aug 2006 05:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.devdawn.com/ettube-brutus-or-ajax/#comment-3021</guid>
		<description>Hey Stu nice links...

The problem I see with AJAX and javascript and the whole Web 2.0 client side performance is that it is not natively supported by browsers and HTML as a standard. Instead of Flash as an intermediate layer... we have a different additional layer on top that is not as easily accessible to all, thus limiting its access and growth rate. 

Also from a coding point of view the javascript being generated is awful and the whole thing feels kludgey, thus the need in GWT for these things to be written in a "proper language" and then "compiled" into javascript. Clearly there is maturing to do in the engine area of Web 2.0. It is not in keeping with the original idea of the web, in marking up text, and to some extent it still could be and would be better off like that.

That being said the functionality is pretty cool and the end-user experience is that of a client-side application running in their browser, which is of course a good step forward from server side page refreshes... which I see as the biggest fundemental change from Web 2.0 so far (even though others do have it encompass a whole lot more, such as concepts like social bookmarking and so on).

What is happening with video lately is interesting, searching Google Video is now a link from their main page...

-- 
&lt;a href="http://codemonkey.sunsite.dk" rel="nofollow"&gt;CodeMonkey&lt;/a&gt; &lt;a href="http://codemonkey.sunsite.dk/blog" rel="nofollow"&gt;Blog&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Hey Stu nice links&#8230;</p>
<p>The problem I see with AJAX and javascript and the whole Web 2.0 client side performance is that it is not natively supported by browsers and HTML as a standard. Instead of Flash as an intermediate layer&#8230; we have a different additional layer on top that is not as easily accessible to all, thus limiting its access and growth rate. </p>
<p>Also from a coding point of view the javascript being generated is awful and the whole thing feels kludgey, thus the need in GWT for these things to be written in a &#8220;proper language&#8221; and then &#8220;compiled&#8221; into javascript. Clearly there is maturing to do in the engine area of Web 2.0. It is not in keeping with the original idea of the web, in marking up text, and to some extent it still could be and would be better off like that.</p>
<p>That being said the functionality is pretty cool and the end-user experience is that of a client-side application running in their browser, which is of course a good step forward from server side page refreshes&#8230; which I see as the biggest fundemental change from Web 2.0 so far (even though others do have it encompass a whole lot more, such as concepts like social bookmarking and so on).</p>
<p>What is happening with video lately is interesting, searching Google Video is now a link from their main page&#8230;</p>
<p>&#8211;<br />
<a href="http://codemonkey.sunsite.dk" rel="nofollow">CodeMonkey</a> <a href="http://codemonkey.sunsite.dk/blog" rel="nofollow">Blog</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
