<?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: Ten Myths of Leopard: 4 Java 6 Abandonment!</title>
	<atom:link href="http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/</link>
	<description>Daniel Eran Dilger in San Francisco</description>
	<lastBuildDate>Sun, 05 Feb 2012 17:03:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: danieleran</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-11612</link>
		<dc:creator>danieleran</dc:creator>
		<pubDate>Thu, 28 Aug 2008 05:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-11612</guid>
		<description>Apple finally added Java SE 6 in April, but only for 64-bit Intel Macs.</description>
		<content:encoded><![CDATA[<p>Apple finally added Java SE 6 in April, but only for 64-bit Intel Macs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ten Myths of Leopard: 5 “Back To My Mac” Security Panic! &#8212; RoughlyDrafted Magazine</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-905</link>
		<dc:creator>Ten Myths of Leopard: 5 “Back To My Mac” Security Panic! &#8212; RoughlyDrafted Magazine</dc:creator>
		<pubDate>Mon, 05 Nov 2007 21:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-905</guid>
		<description>[...] of Leopard: 2 It&#8217;s Only a Service Pack! Ten Myths of Leopard: 3 Nothing New for Developers! Ten Myths of Leopard: 4 Java 6 Abandonment! Ten Myths of Leopard: 5 “Back To My Mac” Security [...]</description>
		<content:encoded><![CDATA[<p>[...] of Leopard: 2 It&#8217;s Only a Service Pack! Ten Myths of Leopard: 3 Nothing New for Developers! Ten Myths of Leopard: 4 Java 6 Abandonment! Ten Myths of Leopard: 5 “Back To My Mac” Security [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wordwarrior</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-861</link>
		<dc:creator>wordwarrior</dc:creator>
		<pubDate>Sun, 04 Nov 2007 19:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-861</guid>
		<description>Apple switched WebObjects to Java over great objections from its developers.

Is there any chance that Apple will switch WO back to Objective-C?

It would be pretty risky if they did so, as this would affect the iTMS and Apple Store.</description>
		<content:encoded><![CDATA[<p>Apple switched WebObjects to Java over great objections from its developers.</p>
<p>Is there any chance that Apple will switch WO back to Objective-C?</p>
<p>It would be pretty risky if they did so, as this would affect the iTMS and Apple Store.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beast Of Bodmin</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-844</link>
		<dc:creator>Beast Of Bodmin</dc:creator>
		<pubDate>Sun, 04 Nov 2007 14:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-844</guid>
		<description>&quot;Mac OS X 10.5 Leopard: October 26, 2003&quot;

2003? I thought the release was delayed :)</description>
		<content:encoded><![CDATA[<p>&#8220;Mac OS X 10.5 Leopard: October 26, 2003&#8243;</p>
<p>2003? I thought the release was delayed :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucky</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-841</link>
		<dc:creator>Lucky</dc:creator>
		<pubDate>Sun, 04 Nov 2007 14:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-841</guid>
		<description>&quot;Ten Myths of Daniel Eran Dilger’s RoughlyDrafted. Myth number one: His blogs are always long and detailed.

Myth busted.&quot;

Totally agree on this one.</description>
		<content:encoded><![CDATA[<p>&#8220;Ten Myths of Daniel Eran Dilger’s RoughlyDrafted. Myth number one: His blogs are always long and detailed.</p>
<p>Myth busted.&#8221;</p>
<p>Totally agree on this one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lmasanti</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-819</link>
		<dc:creator>lmasanti</dc:creator>
		<pubDate>Sun, 04 Nov 2007 02:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-819</guid>
		<description>quote:
&quot;Oh, XServe, XSan, Mail Server, Calendar Server, Ruby/Python… basically all of the new features in Leopard Server. And the fact that, unlike Tiger, Leopard Server shipped simultaneously when Leopard did.&quot;

The hardware and software is used by Apple itself!
And in great extension: Apple&#039;s Store, iTunes, .Mac...
iCal is now used internally...

I do agree with you that &quot;this is directed to the enterprise&quot;, but maybe they are testing it inside the company.

Back to Java, Apple uses WebObjects to drive --almost-- all its internet business. WO is all Java. Is WO Java 6 ready? Or it is best --from Apple&#039;s own needs-- to keep Java 5 going?

As for the &quot;same time release&quot; of Client and Server products, maybe can be due to the delay in Leopard. People in the Server release were probably less involved in iPhone development (the &#039;cause&#039; of Leopard&#039;s delay).

Python and Ruby? I do not know.

As for the iPhone, when asked Jobs said something like &quot;Flash maybe, Java definitively no&quot; (my words).</description>
		<content:encoded><![CDATA[<p>quote:<br />
&#8220;Oh, XServe, XSan, Mail Server, Calendar Server, Ruby/Python… basically all of the new features in Leopard Server. And the fact that, unlike Tiger, Leopard Server shipped simultaneously when Leopard did.&#8221;</p>
<p>The hardware and software is used by Apple itself!<br />
And in great extension: Apple&#8217;s Store, iTunes, .Mac&#8230;<br />
iCal is now used internally&#8230;</p>
<p>I do agree with you that &#8220;this is directed to the enterprise&#8221;, but maybe they are testing it inside the company.</p>
<p>Back to Java, Apple uses WebObjects to drive &#8211;almost&#8211; all its internet business. WO is all Java. Is WO Java 6 ready? Or it is best &#8211;from Apple&#8217;s own needs&#8211; to keep Java 5 going?</p>
<p>As for the &#8220;same time release&#8221; of Client and Server products, maybe can be due to the delay in Leopard. People in the Server release were probably less involved in iPhone development (the &#8217;cause&#8217; of Leopard&#8217;s delay).</p>
<p>Python and Ruby? I do not know.</p>
<p>As for the iPhone, when asked Jobs said something like &#8220;Flash maybe, Java definitively no&#8221; (my words).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mfisher</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-818</link>
		<dc:creator>mfisher</dc:creator>
		<pubDate>Sat, 03 Nov 2007 23:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-818</guid>
		<description>@samkass:

On the embedded, the iPhone is one of the few smartphones that can’t run JavaME applications despite it being an ideal platform for it.

I am unable to run JavaME applications on my Treo 700w. The support docs&#039; only mention of Java is that it cannot be used. I have been unable to identify evidence that the Windows Mobile platform supports Java (or JavaME). So that leaves Blackberry and Symbian as the only significantly-deployed Java-friendly platforms.

As an iPhone owner, lack of Java support (especially as it was clearly documented in the release notes) was certainly not a dealbreaker.</description>
		<content:encoded><![CDATA[<p>@samkass:</p>
<p>On the embedded, the iPhone is one of the few smartphones that can’t run JavaME applications despite it being an ideal platform for it.</p>
<p>I am unable to run JavaME applications on my Treo 700w. The support docs&#8217; only mention of Java is that it cannot be used. I have been unable to identify evidence that the Windows Mobile platform supports Java (or JavaME). So that leaves Blackberry and Symbian as the only significantly-deployed Java-friendly platforms.</p>
<p>As an iPhone owner, lack of Java support (especially as it was clearly documented in the release notes) was certainly not a dealbreaker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LunaticSX</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-817</link>
		<dc:creator>LunaticSX</dc:creator>
		<pubDate>Sat, 03 Nov 2007 22:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-817</guid>
		<description>Apple likes to get all of its ducks in a row before making a big push anywhere. They&#039;ve put a bunch of new stuff in Leopard Server that make it attractive to enterprise, but clearly they&#039;re not done, yet.

Perhaps what Apple is waiting for before making a big push to enterprise is getting Java 6 finished and solid on Leopard.

Since Apple is also good at keeping their marketing message clear and focused in a single area at a time (think, in hindsight, of how ridiculous the rumors were that Apple would announce/release a new MacBook at the same time as Leopard went on sale), they&#039;re not going to mix an enterprise-focused push with the consumer-focused push of the Leopard release. (HP needs to learn a big lesson, here.)

They *could* have delayed the release of Leopard Server until Java 6 was ready for it, and roll them into a big enterprise announcement. Apparently, other than Java 6, Leopard Server was ready to go, though, so they didn&#039;t want to wait. They may have even more in mind for a big enterprise announcement, as well, such as new Xserves, Xsans, and who knows what else, so they&#039;d already have enough to intro there.</description>
		<content:encoded><![CDATA[<p>Apple likes to get all of its ducks in a row before making a big push anywhere. They&#8217;ve put a bunch of new stuff in Leopard Server that make it attractive to enterprise, but clearly they&#8217;re not done, yet.</p>
<p>Perhaps what Apple is waiting for before making a big push to enterprise is getting Java 6 finished and solid on Leopard.</p>
<p>Since Apple is also good at keeping their marketing message clear and focused in a single area at a time (think, in hindsight, of how ridiculous the rumors were that Apple would announce/release a new MacBook at the same time as Leopard went on sale), they&#8217;re not going to mix an enterprise-focused push with the consumer-focused push of the Leopard release. (HP needs to learn a big lesson, here.)</p>
<p>They *could* have delayed the release of Leopard Server until Java 6 was ready for it, and roll them into a big enterprise announcement. Apparently, other than Java 6, Leopard Server was ready to go, though, so they didn&#8217;t want to wait. They may have even more in mind for a big enterprise announcement, as well, such as new Xserves, Xsans, and who knows what else, so they&#8217;d already have enough to intro there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: samkass</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-816</link>
		<dc:creator>samkass</dc:creator>
		<pubDate>Sat, 03 Nov 2007 22:37:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-816</guid>
		<description>With 10.3, Apple released a Java update 1 month later (which was about a year after Sun&#039;s release for Windows).  With 10.4, Apple released a Java update on the same day (about 6 months after Sun&#039;s corresponding release).  I think there was some expectation that, considering their communication about making the Mac the &quot;best Java development platform&quot; and other statements at WWDC, that Apple would close the gap finally with 10.5.  Especially considering 10.5&#039;s delay.

Instead, we&#039;ve regressed to where we were with 10.3-- about a year after Sun&#039;s official release with no corresponding Apple release nor any indication that Java 6 would come soon or ever.  What&#039;s more, there are no details about whether Apple is going to include the newer OpenGL rendering pipelines, the Java2D/JOGL bridges, or other technologies that make Java really fast and first-class on the client with Java 6.

That&#039;s the desktop.  On the embedded, the iPhone is one of the few smartphones that can&#039;t run JavaME applications despite it being an ideal platform for it.  (Apple&#039;s searching for a sandboxed, safe solution-- it already exists!  JavaME!)  On the server, J2EE is taking second fiddle to more recent &quot;language of the month&quot; projects, despite the fact that Java is the most popular enterprise language.

Not that it matters.  I think the loss of trust in Apple after 10.5&#039;s release is going to set them back dramatically in the developer community no matter what they do now.</description>
		<content:encoded><![CDATA[<p>With 10.3, Apple released a Java update 1 month later (which was about a year after Sun&#8217;s release for Windows).  With 10.4, Apple released a Java update on the same day (about 6 months after Sun&#8217;s corresponding release).  I think there was some expectation that, considering their communication about making the Mac the &#8220;best Java development platform&#8221; and other statements at WWDC, that Apple would close the gap finally with 10.5.  Especially considering 10.5&#8217;s delay.</p>
<p>Instead, we&#8217;ve regressed to where we were with 10.3&#8211; about a year after Sun&#8217;s official release with no corresponding Apple release nor any indication that Java 6 would come soon or ever.  What&#8217;s more, there are no details about whether Apple is going to include the newer OpenGL rendering pipelines, the Java2D/JOGL bridges, or other technologies that make Java really fast and first-class on the client with Java 6.</p>
<p>That&#8217;s the desktop.  On the embedded, the iPhone is one of the few smartphones that can&#8217;t run JavaME applications despite it being an ideal platform for it.  (Apple&#8217;s searching for a sandboxed, safe solution&#8211; it already exists!  JavaME!)  On the server, J2EE is taking second fiddle to more recent &#8220;language of the month&#8221; projects, despite the fact that Java is the most popular enterprise language.</p>
<p>Not that it matters.  I think the loss of trust in Apple after 10.5&#8217;s release is going to set them back dramatically in the developer community no matter what they do now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wordwarrior</title>
		<link>http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/comment-page-1/#comment-810</link>
		<dc:creator>wordwarrior</dc:creator>
		<pubDate>Sat, 03 Nov 2007 20:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/2007/11/03/ten-myths-of-leopard-4-java-6-abandonment/#comment-810</guid>
		<description>Let&#039;s not forget Leopard (Intel only) UNIX certification.

If Apple wanted to be clear that it was adding only Java 5, it should have said &quot;Java 5&quot; in its Leopard preview documentation, instead of &quot;Java&quot;.  Plus, Apple released a Java 6 preview for Tiger.  Both of these actions qualify as &quot;led to believe&quot;, in my book.

Secrecy is critical strategy for Apple to sell its consumer products, as it allows them to control the timing and degree of its product announcements (often just as the product is shipping).   It allows them to get free publicity from the media, reducing their need to advertise.  Much of Apple&#039;s success with consumer products stems from Apple&#039;s timed announcements strategy.

However, this simply doesn&#039;t work with developers and enterprise users.  Please explain to me, aside from the deception, how withholding details from Java developers will allow them to sell more hardware and software to them.  Such a strategy, as evidenced by the JavaLobby forum, is having the opposite effect.</description>
		<content:encoded><![CDATA[<p>Let&#8217;s not forget Leopard (Intel only) UNIX certification.</p>
<p>If Apple wanted to be clear that it was adding only Java 5, it should have said &#8220;Java 5&#8243; in its Leopard preview documentation, instead of &#8220;Java&#8221;.  Plus, Apple released a Java 6 preview for Tiger.  Both of these actions qualify as &#8220;led to believe&#8221;, in my book.</p>
<p>Secrecy is critical strategy for Apple to sell its consumer products, as it allows them to control the timing and degree of its product announcements (often just as the product is shipping).   It allows them to get free publicity from the media, reducing their need to advertise.  Much of Apple&#8217;s success with consumer products stems from Apple&#8217;s timed announcements strategy.</p>
<p>However, this simply doesn&#8217;t work with developers and enterprise users.  Please explain to me, aside from the deception, how withholding details from Java developers will allow them to sell more hardware and software to them.  Such a strategy, as evidenced by the JavaLobby forum, is having the opposite effect.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

