<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The future of Java on Macs</title>
	<link>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/</link>
	<description>Alex Miller's technical blog</description>
	<pubDate>Thu, 20 Nov 2008 14:04:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Peter Kirn</title>
		<link>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12527</link>
		<pubDate>Thu, 01 Nov 2007 14:36:03 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12527</guid>
					<description>It's interesting that, for all the criticism of Java, no one questions the idea that the Cocoa and Carbon frameworks have ANY future outside the Mac. The honest truth is, a lot of Mac development is cautious about just how much Cocoa gets used. And those doing cross-platform development start out with cross-platform libraries from the start. I think Java cross-platform development for the desktop is FAR more likely than Cocoa.

Meanwhile, I keep hearing buzz that in fact Java 6 is completely derailed:
http://createdigitalmusic.com/2007/10/31/rumor-mac-javas-demise-is-real-and-why-that-could-be-good-news-for-multimedia/

That's fine with me. There are lots of good reasons for a push for desktop Java, and plenty Java can do that a) Flash/Flex/AIR can't or b) Java can do more easily than C++ development can, depending on the job.

It seems like the desktop is going to have *more* rich clients in the future, not less. But the company to make that play happen is obviously Sun (and the OpenJDK community), not Apple. So, for the time being, the Mac remains just fine for Java 5 deployment, and we can hope that Sun finds a way to finally get development of JDK back in their court and out of Apple's.</description>
		<content:encoded><![CDATA[<p>It&#8217;s interesting that, for all the criticism of Java, no one questions the idea that the Cocoa and Carbon frameworks have ANY future outside the Mac. The honest truth is, a lot of Mac development is cautious about just how much Cocoa gets used. And those doing cross-platform development start out with cross-platform libraries from the start. I think Java cross-platform development for the desktop is FAR more likely than Cocoa.</p>
<p>Meanwhile, I keep hearing buzz that in fact Java 6 is completely derailed:<br />
<a href='http://createdigitalmusic.com/2007/10/31/rumor-mac-javas-demise-is-real-and-why-that-could-be-good-news-for-multimedia/' rel='nofollow'>http://createdigitalmusic.com/2007/10/31/rumor-mac-javas-demise-is-real-and-why-that-could-be-good-news-for-multimedia/</a></p>
<p>That&#8217;s fine with me. There are lots of good reasons for a push for desktop Java, and plenty Java can do that a) Flash/Flex/AIR can&#8217;t or b) Java can do more easily than C++ development can, depending on the job.</p>
<p>It seems like the desktop is going to have *more* rich clients in the future, not less. But the company to make that play happen is obviously Sun (and the OpenJDK community), not Apple. So, for the time being, the Mac remains just fine for Java 5 deployment, and we can hope that Sun finds a way to finally get development of JDK back in their court and out of Apple&#8217;s.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: napyfab:blog&#187; Blog Archive &#187; links for 2007-10-31</title>
		<link>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12478</link>
		<pubDate>Wed, 31 Oct 2007 23:33:14 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12478</guid>
					<description>[...] Alex Miller - The future of Java on Macs (tags: java apple mac osx future development programming) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Alex Miller - The future of Java on Macs (tags: java apple mac osx future development programming) [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Robert</title>
		<link>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12472</link>
		<pubDate>Wed, 31 Oct 2007 20:29:18 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12472</guid>
					<description>Ah sorry then, I misunderstood you. I also think Apple is going to come out with Java6 just like they have delivered before. Even if they didn't, I would fire up Parallels and use it on another OS in a VM. Give up my mac though? Not bloody likely. : )

The RoR and Python stuff was handled mostly OUTSIDE of Apple but with an Apple Techie along. The reason Perl wasn't included was the developer for CamelBones didn't make the timeline.</description>
		<content:encoded><![CDATA[<p>Ah sorry then, I misunderstood you. I also think Apple is going to come out with Java6 just like they have delivered before. Even if they didn&#8217;t, I would fire up Parallels and use it on another OS in a VM. Give up my mac though? Not bloody likely. : )</p>
<p>The RoR and Python stuff was handled mostly OUTSIDE of Apple but with an Apple Techie along. The reason Perl wasn&#8217;t included was the developer for CamelBones didn&#8217;t make the timeline.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alex</title>
		<link>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12470</link>
		<pubDate>Wed, 31 Oct 2007 20:21:32 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12470</guid>
					<description>RoR is hot, Java's not.  Raises the priority.  Plus, I think you're right that porting a JVM is way more work than just including some RoR gems which already existed and worked - just a packaging and testing issue I would think.</description>
		<content:encoded><![CDATA[<p>RoR is hot, Java&#8217;s not.  Raises the priority.  Plus, I think you&#8217;re right that porting a JVM is way more work than just including some RoR gems which already existed and worked - just a packaging and testing issue I would think.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Blair Zajac</title>
		<link>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12469</link>
		<pubDate>Wed, 31 Oct 2007 20:15:56 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/10/31/the-future-of-java-on-macs/#comment-12469</guid>
					<description>I too was disappointed not seeing Java 6 available.

But to your point about engineering resources, Apple took the time to put the Ruby on Rails stack in 10.5, which while web related, will be less likely used then Java applications running on the Desktop.

So maybe they added RoR for the coolness factor, since no-non developer will ever use that.

RoR was probably a much easier port then Java 6 would, since everybody's already running RoR on 10.4 and its well known how to do so.</description>
		<content:encoded><![CDATA[<p>I too was disappointed not seeing Java 6 available.</p>
<p>But to your point about engineering resources, Apple took the time to put the Ruby on Rails stack in 10.5, which while web related, will be less likely used then Java applications running on the Desktop.</p>
<p>So maybe they added RoR for the coolness factor, since no-non developer will ever use that.</p>
<p>RoR was probably a much easier port then Java 6 would, since everybody&#8217;s already running RoR on 10.4 and its well known how to do so.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
