<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The WebApp developer paradigm</title>
	<atom:link href="http://www.em-motion.mobi/2010/07/19/the-webapp-developer-paradigm/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.em-motion.mobi/2010/07/19/the-webapp-developer-paradigm/</link>
	<description>Mobile software development and web technologies</description>
	<lastBuildDate>Wed, 01 Feb 2012 09:04:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Carl</title>
		<link>http://www.em-motion.mobi/2010/07/19/the-webapp-developer-paradigm/comment-page-1/#comment-10250</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Sun, 16 Jan 2011 03:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.em-motion.mobi/?p=191#comment-10250</guid>
		<description>I agree with you that Web page developers will not, in general, be well-prepared to develop Web apps.  However, Java developers with experience developing desktop applications can make the transition to Web app development by using Google Web Toolkit (GWT) to cross-compile their Java code into client-side Javascript that is automatically generated in separate permutations for each of the major browsers.

There&#039;s still a learning curve, but this approach addresses your items A, B, C and D above by allowing code to be developed and maintained in Java, with much less attention required toward accomodating the various browsers and their quirks.

GWT renders less relevant the skills of a Web site developer in overcoming browser quirks, and moves the UI away from hand-coded HTML and toward libraries of pre-programmed widget objects.  CSS is still important, and would be an advantage for someone with a Web development background over someone with OOP native app development skills.  But CSS is a lot easier to learn than OOA/D/P.</description>
		<content:encoded><![CDATA[<p>I agree with you that Web page developers will not, in general, be well-prepared to develop Web apps.  However, Java developers with experience developing desktop applications can make the transition to Web app development by using Google Web Toolkit (GWT) to cross-compile their Java code into client-side Javascript that is automatically generated in separate permutations for each of the major browsers.</p>
<p>There&#8217;s still a learning curve, but this approach addresses your items A, B, C and D above by allowing code to be developed and maintained in Java, with much less attention required toward accomodating the various browsers and their quirks.</p>
<p>GWT renders less relevant the skills of a Web site developer in overcoming browser quirks, and moves the UI away from hand-coded HTML and toward libraries of pre-programmed widget objects.  CSS is still important, and would be an advantage for someone with a Web development background over someone with OOP native app development skills.  But CSS is a lot easier to learn than OOA/D/P.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On-device JavaScript Debugging: Intro &#124; em&#124;Motion</title>
		<link>http://www.em-motion.mobi/2010/07/19/the-webapp-developer-paradigm/comment-page-1/#comment-7489</link>
		<dc:creator>On-device JavaScript Debugging: Intro &#124; em&#124;Motion</dc:creator>
		<pubDate>Tue, 12 Oct 2010 08:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.em-motion.mobi/?p=191#comment-7489</guid>
		<description>[...] Oct, 2010 Categories: Mobile web technology by Marcelo 0 Comments   As I wrote in my previous post, a paradigm shift is going on in Web-App development. The understanding that Web-App development is [...]</description>
		<content:encoded><![CDATA[<p>[...] Oct, 2010 Categories: Mobile web technology by Marcelo 0 Comments   As I wrote in my previous post, a paradigm shift is going on in Web-App development. The understanding that Web-App development is [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

