Comments on: Why should we have to tune the JVM’s memory parameters to run NetBeans acceptably? http://pinderkent.blogsavy.com/archives/146 Just another Blogsavy.com weblog Sat, 11 Oct 2008 05:49:15 +0000 http://wordpress.org/?v=2.5 By: Michael Campbell http://pinderkent.blogsavy.com/archives/146#comment-322 Michael Campbell Mon, 10 Mar 2008 04:23:19 +0000 http://pinderkent.blogsavy.com/archives/159#comment-322 > But Eclipse can require memory tuning parms as well. Sure, it *can* but it generally doesn't. Out of the box, Eclipse runs reasonably well. The author's point here (which you appear to have completely sidestepped) is that Netbeans doesn't. > But Eclipse can require memory tuning parms as well.

Sure, it *can* but it generally doesn’t. Out of the box, Eclipse runs reasonably well. The author’s point here (which you appear to have completely sidestepped) is that Netbeans doesn’t.

]]> By: Patrick Mueller http://pinderkent.blogsavy.com/archives/146#comment-321 Patrick Mueller Sun, 09 Mar 2008 16:50:34 +0000 http://pinderkent.blogsavy.com/archives/159#comment-321 But Eclipse can require memory tuning parms as well. I think what you're pointing out is that it's a shame that many programs using Java require memory tuning. Memory tuning should be relegated to optimization, instead of a pre-req to run the program in the first place. It's a Java problem; Eclipse, NetBeans, any web container you might use, etc all inherit the problem from Java. But Eclipse can require memory tuning parms as well. I think what you’re pointing out is that it’s a shame that many programs using Java require memory tuning. Memory tuning should be relegated to optimization, instead of a pre-req to run the program in the first place. It’s a Java problem; Eclipse, NetBeans, any web container you might use, etc all inherit the problem from Java.

]]>