<?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: Ajax Predictions for 2008</title>
	<atom:link href="http://www.pathf.com/blogs/2007/12/ajax-prediction/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/12/ajax-prediction/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 05 Dec 2008 17:48:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Michael Sync</title>
		<link>http://www.pathf.com/blogs/2007/12/ajax-prediction/#comment-163</link>
		<dc:creator>Michael Sync</dc:creator>
		<pubDate>Wed, 09 Jan 2008 13:13:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=131#comment-163</guid>
		<description>&lt;p&gt;What about Silverlight? &lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>What about Silverlight? </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilia</title>
		<link>http://www.pathf.com/blogs/2007/12/ajax-prediction/#comment-162</link>
		<dc:creator>ilia</dc:creator>
		<pubDate>Wed, 02 Jan 2008 01:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=131#comment-162</guid>
		<description>&lt;p&gt;uhmm craigslist already uses ajax&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>uhmm craigslist already uses ajax</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scriptor</title>
		<link>http://www.pathf.com/blogs/2007/12/ajax-prediction/#comment-161</link>
		<dc:creator>Scriptor</dc:creator>
		<pubDate>Fri, 28 Dec 2007 14:40:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=131#comment-161</guid>
		<description>&lt;p&gt;WinForms and running Silverlight?&lt;br /&gt;
Yea...that definitely sounds like it's following the open source spirit.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>WinForms and running Silverlight?<br />
Yea&#8230;that definitely sounds like it&#8217;s following the open source spirit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: navot</title>
		<link>http://www.pathf.com/blogs/2007/12/ajax-prediction/#comment-160</link>
		<dc:creator>navot</dc:creator>
		<pubDate>Fri, 28 Dec 2007 07:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=131#comment-160</guid>
		<description>&lt;p&gt;how about this pardigim, Visual WebGui which lets develop pure WinForms with complete abstraction of the AJAX connection, running Silverlight on the client side, with by desgine secured connections (no-logic, no - data client. you get extra productive,you get security, you get unlimited size and wighet application support (client side is indiffrence to application size and wieght, you get your eye canddy and it is all available open source...sounds like the ultimate solution? it looks like it &lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>how about this pardigim, Visual WebGui which lets develop pure WinForms with complete abstraction of the AJAX connection, running Silverlight on the client side, with by desgine secured connections (no-logic, no - data client. you get extra productive,you get security, you get unlimited size and wighet application support (client side is indiffrence to application size and wieght, you get your eye canddy and it is all available open source&#8230;sounds like the ultimate solution? it looks like it </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T.J.</title>
		<link>http://www.pathf.com/blogs/2007/12/ajax-prediction/#comment-159</link>
		<dc:creator>T.J.</dc:creator>
		<pubDate>Thu, 27 Dec 2007 17:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=131#comment-159</guid>
		<description>&lt;p&gt;I myself feel that FireFox has some serious memory issues too...&lt;/p&gt;

&lt;p&gt;Have you used FF3 at all?  For personal use it's now become my default browser (still develop in FF2 because of the plethora of plugins).&lt;/p&gt;

&lt;p&gt;Here's some of my own additions.&lt;/p&gt;

&lt;p&gt;11. Standards will see a huge push forward.  Large websites will start designing with accessibility and usability in mind due to the coming influx of mobile browsers.  While this includes things like HTML/CSS (due to HTML 5), it also means ajax frameworks and server-side communication will become more standardized.  Every mobile device manufacturer will try to implement their own browser with full application support, so some standards will be required to ensure your content is accessible to everyone.&lt;/p&gt;

&lt;p&gt;12. Widgets will rule.  Everyone wants all their content in one place.  Expect more and more websites to support customized widgets for others to use on their pages, as well as developing their own widgets for Facebook, iGoogle, etc.  This will also push stand alone desktop web apps to the mass market (via Adobe AIR and Google Gears).  &lt;/p&gt;

&lt;p&gt;13. Microsoft will release IE8 about ~6 months behind FF3 and will try to one up its feature set (and fail).  They will slim down IE8 (remove the bloat), then add more features to stay competitive, and the bloat comes back.  About the same time FF4 alpha will come out.  They will also add better extension support (similar to Mozilla), however will restrict the functionality of it, causing it to be to much of a hassle for most developers.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I myself feel that FireFox has some serious memory issues too&#8230;</p>
<p>Have you used FF3 at all?  For personal use it&#8217;s now become my default browser (still develop in FF2 because of the plethora of plugins).</p>
<p>Here&#8217;s some of my own additions.</p>
<p>11. Standards will see a huge push forward.  Large websites will start designing with accessibility and usability in mind due to the coming influx of mobile browsers.  While this includes things like HTML/CSS (due to HTML 5), it also means ajax frameworks and server-side communication will become more standardized.  Every mobile device manufacturer will try to implement their own browser with full application support, so some standards will be required to ensure your content is accessible to everyone.</p>
<p>12. Widgets will rule.  Everyone wants all their content in one place.  Expect more and more websites to support customized widgets for others to use on their pages, as well as developing their own widgets for Facebook, iGoogle, etc.  This will also push stand alone desktop web apps to the mass market (via Adobe AIR and Google Gears).  </p>
<p>13. Microsoft will release IE8 about ~6 months behind FF3 and will try to one up its feature set (and fail).  They will slim down IE8 (remove the bloat), then add more features to stay competitive, and the bloat comes back.  About the same time FF4 alpha will come out.  They will also add better extension support (similar to Mozilla), however will restrict the functionality of it, causing it to be to much of a hassle for most developers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Schultz</title>
		<link>http://www.pathf.com/blogs/2007/12/ajax-prediction/#comment-158</link>
		<dc:creator>Robert Schultz</dc:creator>
		<pubDate>Thu, 27 Dec 2007 15:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=131#comment-158</guid>
		<description>&lt;p&gt;&gt;&gt;&gt; 5. MS Volta will do nothing. It is just a FUD shot across the bow of GWT.&lt;br /&gt;
Yup. I 100% Agree.&lt;/p&gt;

&lt;p&gt;&gt;&gt; 9. With the new browsers, a cross platform Canvas/SVG will be a reality by the end of the year.&lt;/p&gt;

&lt;p&gt;Uhm... we are there now?&lt;br /&gt;
Opera, Safari and Firefox all support Canvas.&lt;br /&gt;
With excanvas you have support for Canvas in IE.&lt;br /&gt;
Even the next version of Konqueror (subversion) has Canvas support.&lt;/p&gt;

&lt;p&gt;This is pretty good support in all browsers.&lt;/p&gt;

&lt;p&gt;I don't see any use for SVG right now thanks to Canvas and excanvas.&lt;/p&gt;

&lt;p&gt;&lt;br /&gt;
&gt;&gt;&gt; 10. IE8 will still leak memory like a sieve.&lt;/p&gt;

&lt;p&gt;I myself feel that FireFox has some serious memory issues too...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>>>> 5. MS Volta will do nothing. It is just a FUD shot across the bow of GWT.<br />
Yup. I 100% Agree.</p>
<p>>> 9. With the new browsers, a cross platform Canvas/SVG will be a reality by the end of the year.</p>
<p>Uhm&#8230; we are there now?<br />
Opera, Safari and Firefox all support Canvas.<br />
With excanvas you have support for Canvas in IE.<br />
Even the next version of Konqueror (subversion) has Canvas support.</p>
<p>This is pretty good support in all browsers.</p>
<p>I don&#8217;t see any use for SVG right now thanks to Canvas and excanvas.</p>
<p>
>>> 10. IE8 will still leak memory like a sieve.</p>
<p>I myself feel that FireFox has some serious memory issues too&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
