<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://ajax.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Mike Padilla</title>
 <link>http://ajax.sys-con.com/</link>
 <description>Latest articles from Mike Padilla</description>
 <language>en</language>
 <copyright>Copyright 2009 </copyright>
 <generator></generator>
 <lastBuildDate>Tue, 06 Jan 2009 06:06:54 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Prescribing AJAX: Panacea, Placebo, or Poison? Peeling the AJAX Onion</title>
 <link>http://ajax.sys-con.com/node/470384</link>
 <description>Ever since Jesse James Garrett coined the term AJAX to describe the collection of existing technologies that allow increased responsiveness and interactivity of webpages, its adoption has been embraced across the Web. But have designers and developers gone overboard? Is everything a nail to be pounded with the AJAX hammer? Some of the fundamental technologies that AJAX is based on, including HTML, CSS, and JavaScript, can sometimes offer simpler, more elegant solutions that are better suited to certain user experiences.&lt;p&gt;&lt;a href=&quot;http://ajax.sys-con.com/node/470384&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 05 Dec 2007 10:30:00 EST</pubDate>
 <guid isPermaLink="true">http://ajax.sys-con.com/node/470384</guid>
</item>
</channel>
</rss>
