<?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"
	>
<channel>
	<title>Comments on: JavaFX - Another Ajax Killer</title>
	<atom:link href="http://www.pathf.com/blogs/2007/05/javafx_another_/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/05/javafx_another_/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 05 Dec 2008 11:17:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Dave</title>
		<link>http://www.pathf.com/blogs/2007/05/javafx_another_/#comment-453</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 09 May 2007 23:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=343#comment-453</guid>
		<description>&lt;p&gt;Flash, Silveright, and JavaFX aren't positioned to be AJAX killers.  AJAX is what the baseline of the web experience will become.  Because of its inherent technical limitations, AJAX doesn't compete with Flash or Silveright &lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Flash, Silveright, and JavaFX aren&#8217;t positioned to be AJAX killers.  AJAX is what the baseline of the web experience will become.  Because of its inherent technical limitations, AJAX doesn&#8217;t compete with Flash or Silveright </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricky Clarkson</title>
		<link>http://www.pathf.com/blogs/2007/05/javafx_another_/#comment-452</link>
		<dc:creator>Ricky Clarkson</dc:creator>
		<pubDate>Wed, 09 May 2007 16:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=343#comment-452</guid>
		<description>&lt;p&gt;There's nothing wrong with dynamic typing, as long as you can statically analyse the code too (plus give hints to static analysers).  Mandatory static typing increases dependencies between modules, leading to more monolithic code.&lt;/p&gt;

&lt;p&gt;I like Bracha's pluggable types - add type annotations when you feel like it, but if your type annotations don't match, that doesn't stop programs from running.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>There&#8217;s nothing wrong with dynamic typing, as long as you can statically analyse the code too (plus give hints to static analysers).  Mandatory static typing increases dependencies between modules, leading to more monolithic code.</p>
<p>I like Bracha&#8217;s pluggable types - add type annotations when you feel like it, but if your type annotations don&#8217;t match, that doesn&#8217;t stop programs from running.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asd</title>
		<link>http://www.pathf.com/blogs/2007/05/javafx_another_/#comment-451</link>
		<dc:creator>Asd</dc:creator>
		<pubDate>Wed, 09 May 2007 16:40:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=343#comment-451</guid>
		<description>&lt;p&gt;JavaFX (or F3) is statically typed (with type inference I think).&lt;br /&gt;
But it really is an embarrassment. F3 was OK for what it was. It is not an Ajax or Flash killer. There is no sound or video support. There is no nonlinear animation. There is no graphical designer. Their examples are half working imitations of other people's Flash sites (copyright infringing images and all).&lt;/p&gt;

&lt;p&gt;F3 was a hobby project, and it is nowhere near ready for real use.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>JavaFX (or F3) is statically typed (with type inference I think).<br />
But it really is an embarrassment. F3 was OK for what it was. It is not an Ajax or Flash killer. There is no sound or video support. There is no nonlinear animation. There is no graphical designer. Their examples are half working imitations of other people&#8217;s Flash sites (copyright infringing images and all).</p>
<p>F3 was a hobby project, and it is nowhere near ready for real use.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
