<?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: JTeam Technology Matrix: The Stars</title>
	<atom:link href="http://blog.jteam.nl/2009/09/07/jteam-technology-matrix-the-stars/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jteam.nl/2009/09/07/jteam-technology-matrix-the-stars/</link>
	<description>Keep updated on what we&#039;re doing!</description>
	<lastBuildDate>Sat, 04 Sep 2010 13:07:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: DailyNetBlog.com</title>
		<link>http://blog.jteam.nl/2009/09/07/jteam-technology-matrix-the-stars/comment-page-1/#comment-713</link>
		<dc:creator>DailyNetBlog.com</dc:creator>
		<pubDate>Mon, 21 Sep 2009 23:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jteam.nl/?p=797#comment-713</guid>
		<description>[...] JTeam Technology Matrix: The Stars « JTeam Blog / JTeam &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] JTeam Technology Matrix: The Stars « JTeam Blog / JTeam &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uri Boness</title>
		<link>http://blog.jteam.nl/2009/09/07/jteam-technology-matrix-the-stars/comment-page-1/#comment-667</link>
		<dc:creator>Uri Boness</dc:creator>
		<pubDate>Tue, 08 Sep 2009 12:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jteam.nl/?p=797#comment-667</guid>
		<description>@Itay

I totally understand and appreciate your opinion on the subject. From my experience this is very much a subjective issue. We&#039;re talking about two completely different programming styles - some people feel more comfortable with a markup language while others (perhaps those who&#039;re more Java and Swing oriented). Personally, I find the &quot;Swing-like&quot; style easier to grasp and develop and the fact that all code (presentation and logic) is written in one language makes it easier *for me* to work with and maintain. Another aspect to consider is that type of application you&#039;re actually developing. I think it is very important to choose the right technology for the right problem. If you ask me, I wouldn&#039;t go ahead and for example develop a public website with GWT simple because I don&#039;t believe it&#039;s the right technology (there are more issues than development style here to consider - SEO for example). In JTeam we see GWT as a perfect technology for developing back office and management consoles applications, in which the richness of the UI is much more evident and plays a stronger role. That all being said, the good news is that the next GWT release (2.0) will come with support for template binding - that is, you&#039;ll be able to define your UI in a markup language and bind it to the GWT java code.</description>
		<content:encoded><![CDATA[<p>@Itay</p>
<p>I totally understand and appreciate your opinion on the subject. From my experience this is very much a subjective issue. We&#8217;re talking about two completely different programming styles &#8211; some people feel more comfortable with a markup language while others (perhaps those who&#8217;re more Java and Swing oriented). Personally, I find the &#8220;Swing-like&#8221; style easier to grasp and develop and the fact that all code (presentation and logic) is written in one language makes it easier *for me* to work with and maintain. Another aspect to consider is that type of application you&#8217;re actually developing. I think it is very important to choose the right technology for the right problem. If you ask me, I wouldn&#8217;t go ahead and for example develop a public website with GWT simple because I don&#8217;t believe it&#8217;s the right technology (there are more issues than development style here to consider &#8211; SEO for example). In JTeam we see GWT as a perfect technology for developing back office and management consoles applications, in which the richness of the UI is much more evident and plays a stronger role. That all being said, the good news is that the next GWT release (2.0) will come with support for template binding &#8211; that is, you&#8217;ll be able to define your UI in a markup language and bind it to the GWT java code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Itay Maman</title>
		<link>http://blog.jteam.nl/2009/09/07/jteam-technology-matrix-the-stars/comment-page-1/#comment-657</link>
		<dc:creator>Itay Maman</dc:creator>
		<pubDate>Mon, 07 Sep 2009 13:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jteam.nl/?p=797#comment-657</guid>
		<description>I often felt that GWT is not a good UI solution. It seems that object-oriented languages are quite verbose with respect to UI code and that hierarchical (XML) languages are better in this aspect. From this perspective, GWT maximizes the *disadvantages*. I&#039;d be interested to hear your thoughts about GWT.</description>
		<content:encoded><![CDATA[<p>I often felt that GWT is not a good UI solution. It seems that object-oriented languages are quite verbose with respect to UI code and that hierarchical (XML) languages are better in this aspect. From this perspective, GWT maximizes the *disadvantages*. I&#8217;d be interested to hear your thoughts about GWT.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
