<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://flex.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Richard Monson-Haefel</title>
 <link>http://flex.sys-con.com/</link>
 <description>Latest articles from Richard Monson-Haefel</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Wed, 20 Aug 2008 19:09:04 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>AJAX RIA News - Which Technologies Will Carry the Rich Internet Torch?</title>
 <link>http://flex.sys-con.com/node/510792</link>
 <description>If Gartner&#039;s assessment of AJAX&#039;s position on the Hype Cycle is correct, then the days when AJAX is the only game in town are over. Enter the age of what Anne Thomas Manes of the Burton Group calls &#039;Fit Clients&#039; - a hybrid of Thick Clients (a.k.a. Fat Clients) and Thin Clients (HTML and RIA). Adobe AIR is definitely a Fit Client technology, but it&#039;s not the first and won&#039;t be the only player in this space.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/510792&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 17 Jun 2008 07:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/510792</guid>
</item>
<item>
 <title>AJAX RIA World - The Tale of Two Webs</title>
 <link>http://flex.sys-con.com/node/560597</link>
 <description>When talking about the &#039;web&#039; what are we referring to? For most people it&#039;s what can be experienced through their web browser including HTML, audio and video streaming, Flash-based animation, or rich Internet Application (RIA) interfaces. The key to this perspective is the web browser, which is viewed as essential for experiencing any type of content available via a hyperlink on the web.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/560597&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 27 May 2008 14:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/560597</guid>
</item>
<item>
 <title>The Next Battle for the Desktop</title>
 <link>http://flex.sys-con.com/node/548350</link>
 <description>The computer desktop today is what the television was to people in the 1980s. It&#039;s the single most important channel for consumer entertainment and information. The computer desktop - as was the case with newspapers before there was radio and radio before there was television - has become the high ground from which empires are built.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/548350&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 27 Apr 2008 10:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/548350</guid>
</item>
<item>
 <title>Engelbart&#039;s Usability Dilemma: Efficiency vs Ease-of-Use</title>
 <link>http://flex.sys-con.com/node/536976</link>
 <description>The mouse was the original idea of Doug Engelbart who was the head of the Augmentation Research Center (ARC) at Stanford Research Institute. Engelbart&#039;s philosophy is best embodied, in my opinion, in the design of another device that he invented, the five-finger keyboard - with keys like a piano, used by one hand. The problem was, Engelbart&#039;s five-finger keyboard and mouse combination was very difficult to learn.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/536976&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 10 Apr 2008 09:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/536976</guid>
</item>
<item>
 <title>The &quot;Uncanny Valley&quot; Theory Doesn&#039;t Apply to Desktop UI</title>
 <link>http://flex.sys-con.com/node/531419</link>
 <description>If you design an application that runs on Windows but doesn&#039;t look exactly like Windows, so the old argument goes, the effect will be unsettling for users. But sticking to the native look and feel (L&amp;F) should not be the end-goal of designers.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/531419&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 02 Apr 2008 14:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/531419</guid>
</item>
<item>
 <title>Enterprise Widgets: The Story So Far</title>
 <link>http://flex.sys-con.com/node/524527</link>
 <description>Desktop widgets have been around for a very long time. The first set of desktop widgets were introduced by Apple back in 1983 with their release of Apple Desktop Accessories. Obviously Apple was way ahead of the curve, but these early widgets were not Internet enabled - the popular Internet, as we know it, didn&#039;t exist - so their utility was pretty limited.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/524527&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 30 Mar 2008 02:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/524527</guid>
</item>
<item>
 <title>The Grand Convergence: Web + RIA + Widgets + Client/Server</title>
 <link>http://flex.sys-con.com/node/516151</link>
 <description>For the past ten years application developers have been stuck with only two desktop client choices. Traditionally, they can choose either a very thin Web-client technology implemented in HTML and CSS, or a very heavyweight thick client experience implemented using traditional client/server (C/S) technologies (e.g. Java Swing, MFC). It wasn&#039;t until the introduction of RIA technologies (e.g. AJAX, Adobe Flex, Curl, and Silverlight) and widget engines (e.g. Yahoo! Widgets and Google Gadgets) that we were given more options.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/516151&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 13 Mar 2008 06:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/516151</guid>
</item>
<item>
 <title>Why Microsoft Loves Google Android, Take 2</title>
 <link>http://flex.sys-con.com/node/478686</link>
 <description>Android is not bad like world hunger is bad, it&#039;s just not good for existing Java standards. My main thesis is this: If Android succeeds as it is currently defined then the entire Java platform, including Java SE, is in trouble. Android&#039;s success sends a clear message: Standardization of Java is not important; Write once, run anywhere is not important. That&#039;s the antithesis of what the Java platform is all about.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/478686&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 25 Dec 2007 10:30:00 EST</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/478686</guid>
</item>
<item>
 <title>Why Microsoft Loves Google&#039;s Android</title>
 <link>http://flex.sys-con.com/node/467328</link>
 <description>You won&#039;t hear Microsoft say this out loud, but secretly they are celebrating Google&#039;s contribution of the Android mobile phone platform to the Open Handset Alliance. At least they ought to be. Android is perhaps the best thing to happen to Microsoft since they won the browser wars in the 1990s.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/467328&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 29 Nov 2007 16:00:00 EST</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/467328</guid>
</item>
<item>
 <title>Guaranteed Messaging With JMS</title>
 <link>http://flex.sys-con.com/node/36239</link>
 <description>The notion of guaranteed delivery of Java Message Service messages has been lightly touched on in other recently published articles on JMS. But what really makes a JMS message &#039;guaranteed&#039;? Should you just take it on faith, or would you like to know what&#039;s behind it?&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/36239&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 01 Apr 2001 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/36239</guid>
</item>
<item>
 <title>Design Patterns</title>
 <link>http://flex.sys-con.com/node/35808</link>
 <description>Design Patterns are blueprints that describe how to design class structures and object interactions to solve commonly encountered problems. A Design Pattern can be as simple as the practice of using an interface to achieve polymorphism and as complicated as designs used to solve intricate concurrency problems.&lt;p&gt;&lt;a href=&quot;http://flex.sys-con.com/node/35808&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 01 Jun 1997 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://flex.sys-con.com/node/35808</guid>
</item>
</channel>
</rss>
