<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Articles by Richard Monson-Haefel</title>
<link>http://web2.sys-con.com/</link>
<description>Latest articles from Richard Monson-Haefel</description>
<copyright>Copyright 2008 WEB 2.0 JOURNAL</copyright>
<lastBuildDate>Sat, 05 Jul 2008 17:15:00 GMT</lastBuildDate>
<generator>WEB 2.0 JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>AJAX RIA News - Which Technologies Will Carry the Rich Internet Torch?</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/510792.htm</guid><link>http://web2.sys-con.com/read/510792.htm</link>
<pubDate>Tue, 17 Jun 2008 07:30:00 GMT</pubDate>
<description>If Gartner&apos;s assessment of AJAX&apos;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 &apos;Fit Clients&apos; - 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&apos;s not the first and won&apos;t be the only player in this space.</description>

</item><item>
<title>AJAX RIA World - The Tale of Two Webs</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/560597.htm</guid><link>http://web2.sys-con.com/read/560597.htm</link>
<pubDate>Tue, 27 May 2008 14:45:00 GMT</pubDate>
<description>When talking about the &apos;web&apos; what are we referring to? For most people it&apos;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.</description>

</item><item>
<title>The Next Battle for the Desktop</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/548350.htm</guid><link>http://web2.sys-con.com/read/548350.htm</link>
<pubDate>Sun, 27 Apr 2008 10:30:00 GMT</pubDate>
<description>The computer desktop today is what the television was to people in the 1980s. It&apos;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.</description>

</item><item>
<title>Engelbart&apos;s Usability Dilemma: Efficiency vs Ease-of-Use</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/536976.htm</guid><link>http://web2.sys-con.com/read/536976.htm</link>
<pubDate>Thu, 10 Apr 2008 09:15:00 GMT</pubDate>
<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&apos;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&apos;s five-finger keyboard and mouse combination was very difficult to learn.</description>

</item><item>
<title>The &quot;Uncanny Valley&quot; Theory Doesn&apos;t Apply to Desktop UI</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/531419.htm</guid><link>http://web2.sys-con.com/read/531419.htm</link>
<pubDate>Wed, 02 Apr 2008 14:45:00 GMT</pubDate>
<description>If you design an application that runs on Windows but doesn&apos;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.</description>

</item><item>
<title>Enterprise Widgets: The Story So Far</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/524527.htm</guid><link>http://web2.sys-con.com/read/524527.htm</link>
<pubDate>Sun, 30 Mar 2008 02:45:00 GMT</pubDate>
<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&apos;t exist - so their utility was pretty limited.</description>

</item><item>
<title>The Grand Convergence: Web + RIA + Widgets + Client/Server</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/516151.htm</guid><link>http://web2.sys-con.com/read/516151.htm</link>
<pubDate>Thu, 13 Mar 2008 06:30:00 GMT</pubDate>
<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&apos;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.</description>

</item><item>
<title>Why Microsoft Loves Google Android, Take 2</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/478686.htm</guid><link>http://web2.sys-con.com/read/478686.htm</link>
<pubDate>Tue, 25 Dec 2007 10:30:00 GMT</pubDate>
<description>Android is not bad like world hunger is bad, it&apos;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&apos;s success sends a clear message: Standardization of Java is not important; Write once, run anywhere is not important. That&apos;s the antithesis of what the Java platform is all about.</description>

</item><item>
<title>Why Microsoft Loves Google&apos;s Android</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/467328.htm</guid><link>http://web2.sys-con.com/read/467328.htm</link>
<pubDate>Thu, 29 Nov 2007 16:00:00 GMT</pubDate>
<description>You won&apos;t hear Microsoft say this out loud, but secretly they are celebrating Google&apos;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.</description>

</item><item>
<title>Guaranteed Messaging With JMS</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/36239.htm</guid><link>http://web2.sys-con.com/read/36239.htm</link>
<pubDate>Sun, 01 Apr 2001 00:00:00 GMT</pubDate>
<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 &apos;guaranteed&apos;? Should you just take it on faith, or would you like to know what&apos;s behind it?</description>

</item><item>
<title>Design Patterns</title>
<guid isPermaLink="true">http://web2.sys-con.com/read/35808.htm</guid><link>http://web2.sys-con.com/read/35808.htm</link>
<pubDate>Sun, 01 Jun 1997 00:00:00 GMT</pubDate>
<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.</description>

</item></channel></rss>