<?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: Eclipse + OS X = unhappy</title>
	<atom:link href="http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/feed/" rel="self" type="application/rss+xml" />
	<link>http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/</link>
	<description>Ramblings on Java, Wicket, cats and other stuff</description>
	<lastBuildDate>Wed, 27 Jan 2010 00:31:04 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Objective-C rocks</title>
		<link>http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/comment-page-1/#comment-57857</link>
		<dc:creator>Objective-C rocks</dc:creator>
		<pubDate>Sat, 09 Jan 2010 09:40:16 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-57857</guid>
		<description>I&#039;ve studied J2ME, J2SE and J2EE for two years but then I discovered Objective-C. I switched and regard this as the best decision I have ever made. I suggest that others do the same. I found the class libraries to be works of art - the documentation excellent and the development tools to be far superior to anything I&#039;ve used before. I&#039;ve programmed on various platforms and various languages- in windows linux OSX and a few handhelds. I remember the disappointment and frustration caused by badly designed components and that the only way I could achieve my goals most times was to rewrite those components from scratch. Even this wasn&#039;t enough when one implementation of the same API differs from the next - even devices created by the same manufacturers supposedly implementing the same APIs broke basic functionality like that buttons were mapped to the wrong keys.

Open source is great only because its free - it is inferior in all other regards and that is to be expected if you understand that money translates into time, effort and expertise being allocated to making something the best it can be. Why not pay people what they justly deserve for delivering outstanding work? Work that improves quality of life (for programmers that is) and gives us peace of mind. I have never once experienced the frustrations and disappointments in Objective-C and Cocoa that I used to on a nearly daily basis with open source. Although you finally get the job done its how you get it done that makes the difference. I can finish an objective-c project with a smile on my face but the same project in Java makes me want to find the authors of some of these components and classes and just ask them what the hell they were smoking at the time - or just suggest they get another day job or a different hobby. I can&#039;t say the same about Cocoa and Objective-C. I know it was written by veteran software engineers so if I do find something wrong its going to be something small and insignificant - so far I&#039;m happy - I&#039;ve been happy for over a year now and thats a record no Java worshipper can beat. I&#039;d like to have liked Java - hell I spent a great deal of money and time hoping to become an &quot;expert&quot; but I&#039;ve just been disappointed too many times.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve studied J2ME, J2SE and J2EE for two years but then I discovered Objective-C. I switched and regard this as the best decision I have ever made. I suggest that others do the same. I found the class libraries to be works of art &#8211; the documentation excellent and the development tools to be far superior to anything I&#8217;ve used before. I&#8217;ve programmed on various platforms and various languages- in windows linux OSX and a few handhelds. I remember the disappointment and frustration caused by badly designed components and that the only way I could achieve my goals most times was to rewrite those components from scratch. Even this wasn&#8217;t enough when one implementation of the same API differs from the next &#8211; even devices created by the same manufacturers supposedly implementing the same APIs broke basic functionality like that buttons were mapped to the wrong keys.</p>
<p>Open source is great only because its free &#8211; it is inferior in all other regards and that is to be expected if you understand that money translates into time, effort and expertise being allocated to making something the best it can be. Why not pay people what they justly deserve for delivering outstanding work? Work that improves quality of life (for programmers that is) and gives us peace of mind. I have never once experienced the frustrations and disappointments in Objective-C and Cocoa that I used to on a nearly daily basis with open source. Although you finally get the job done its how you get it done that makes the difference. I can finish an objective-c project with a smile on my face but the same project in Java makes me want to find the authors of some of these components and classes and just ask them what the hell they were smoking at the time &#8211; or just suggest they get another day job or a different hobby. I can&#8217;t say the same about Cocoa and Objective-C. I know it was written by veteran software engineers so if I do find something wrong its going to be something small and insignificant &#8211; so far I&#8217;m happy &#8211; I&#8217;ve been happy for over a year now and thats a record no Java worshipper can beat. I&#8217;d like to have liked Java &#8211; hell I spent a great deal of money and time hoping to become an &#8220;expert&#8221; but I&#8217;ve just been disappointed too many times.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Michalski</title>
		<link>http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/comment-page-1/#comment-56960</link>
		<dc:creator>Tim Michalski</dc:creator>
		<pubDate>Wed, 11 Jun 2008 22:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56960</guid>
		<description>Xcode?? That takes up way too much memory. Why not just use vi or emacs on the terminal for coding. In fact, it would really help if you disabled the Mac OSX user interface and just booted into the console. You&#039;d probably not have any more IDE issues then. ;)

I&#039;m having the same issues and figured that I would just put a hammer through my monitor. The JVM &amp; Kernel quickly stopped bickering and started bi-lateral communications with all parties involved.</description>
		<content:encoded><![CDATA[<p>Xcode?? That takes up way too much memory. Why not just use vi or emacs on the terminal for coding. In fact, it would really help if you disabled the Mac OSX user interface and just booted into the console. You&#8217;d probably not have any more IDE issues then. <img src='http://martijndashorst.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>I&#8217;m having the same issues and figured that I would just put a hammer through my monitor. The JVM &amp; Kernel quickly stopped bickering and started bi-lateral communications with all parties involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Peterson</title>
		<link>http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/comment-page-1/#comment-56935</link>
		<dc:creator>Matthew Peterson</dc:creator>
		<pubDate>Fri, 06 Jun 2008 03:36:44 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56935</guid>
		<description>Just use Xcode or any editor that does syntax highlighting instead of wasting time with an IDE......then you can allocate that RAM to JVM instead of to the IDE</description>
		<content:encoded><![CDATA[<p>Just use Xcode or any editor that does syntax highlighting instead of wasting time with an IDE&#8230;&#8230;then you can allocate that RAM to JVM instead of to the IDE</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: srecko toroman</title>
		<link>http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/comment-page-1/#comment-56897</link>
		<dc:creator>srecko toroman</dc:creator>
		<pubDate>Thu, 22 May 2008 23:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56897</guid>
		<description>Well it only happens with Eclipse 3.3 Enterprise Edition on Unix platforms. For example Classic eclipse (*without some plugins e.g. mylyn*) has never crashed on my Debian. 

Anyway, Eclipse is just great for being a powerful platform, SWT is great too, but it is not quite perfect, yet :)</description>
		<content:encoded><![CDATA[<p>Well it only happens with Eclipse 3.3 Enterprise Edition on Unix platforms. For example Classic eclipse (*without some plugins e.g. mylyn*) has never crashed on my Debian. </p>
<p>Anyway, Eclipse is just great for being a powerful platform, SWT is great too, but it is not quite perfect, yet <img src='http://martijndashorst.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harald Walker</title>
		<link>http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/comment-page-1/#comment-56862</link>
		<dc:creator>Harald Walker</dc:creator>
		<pubDate>Fri, 16 May 2008 23:15:44 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56862</guid>
		<description>How much RAM does your Mac have? For over a year I had 2 GB and most of the time it went very well with Mac OS X (first Tiger, then Leopard) and Eclipse (3.3.2, 3.3.3). When I started running multiple Eclipse instances next to each other plus Oracle XE on a Linux VM and the usual other programs (Firefox, Thunderbird,...) things started to get unbearable slow. I&#039;ve since the upgraded the hard disk in my MacBook Pro to a 7200 rpm drive and added another 2GB of memory. That helped a lot and everything is running fine. I&#039;ve never had problems with crashing Eclipse (except when a memory module was defect).</description>
		<content:encoded><![CDATA[<p>How much RAM does your Mac have? For over a year I had 2 GB and most of the time it went very well with Mac OS X (first Tiger, then Leopard) and Eclipse (3.3.2, 3.3.3). When I started running multiple Eclipse instances next to each other plus Oracle XE on a Linux VM and the usual other programs (Firefox, Thunderbird,&#8230;) things started to get unbearable slow. I&#8217;ve since the upgraded the hard disk in my MacBook Pro to a 7200 rpm drive and added another 2GB of memory. That helped a lot and everything is running fine. I&#8217;ve never had problems with crashing Eclipse (except when a memory module was defect).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
