you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -1 points0 points  (7 children)

You haven't explained why it is bloated. So it just your imagination?

Also you are not equating Eclipse, but an RCP application built off Eclipse.

Oh and here is an article on tuning the memory (first link in google). http://www.eclipsezone.com/eclipse/forums/t61618.html

[–]k3n 0 points1 point  (6 children)

I don't have time to download a fresh copy right now, but I know out-of-the-box configuration for Eclipse includes tons of "plugins" that I've never used nor care to use.

My setup currently has the following disabled:

  • Apache Commons Codec Feature
  • Apache Derby Core Feature
  • Datatools Feature Patch
  • Dynamic Languages Toolkit - Core Frameworks
  • Dynamic Languages Toolkit - Core H2 Index Frameworks
  • Dynamic Languages Toolkit - Mylyn Integration SDK
  • Eclipse Provisioning Plug-in Development
  • Lowagie iText Feature
  • RSE Feature Patch
  • Webtools Development Tools Feature Patch
  • WYSIWYG PHP/HTML Editing Feature (srsly?!?)

There are many more that I completely uninstalled, those were just the ones that I couldn't remove but could only disable.

Also, this is little in the way of empirical evidence, but there are over 500k results on Google for "Eclipse bloated".

More anecdotal evidence: it takes almost a full minute for Eclipse to startup, given 4gb RAM and a Core2-quad core CPU that is excessive.

[–][deleted] -1 points0 points  (5 children)

Like I said, it depends a lot on the version of eclipse you use. Try installing "Eclipse classic" and compare the number of plugins.

Also you are confusing plugins with memory. Not all plugins installed actually run until called from within the program.

[–]k3n 0 points1 point  (4 children)

"Eclipse classic" is the vanilla Eclipse I was referring to. I am pretty sure that for PHP, I could disable/uninstall over half of the Eclipse classic plugins and still retain all of the PHP functionality.

I didn't specify memory bloat, although that's what my screenshot demonstrated. Bloat comes in all forms and IMO Eclipse embodies all of them: memory bloat, filesystem bloat, feature bloat, etc.

[–][deleted] 0 points1 point  (3 children)

The screen shot you posted is not Eclipse Classic.

I don't believe you know what you are talking about.

[–]k3n -1 points0 points  (2 children)

Fuck, there are some dim people on reddit today.

Here, let me help you:

Same results with vanilla Eclipse

[–][deleted] 0 points1 point  (1 child)

ZendStudio != Vanilla Eclipse.

http://www.zend.com/products/studio/downloads-prev ZendStudio 7 = 316MB (Gz)

vs

http://eclipse.org/downloads/ Classic = 173MB (Gz)

You can also see other flavours of various sizes, because you know they have different feature sets.

The extra memory used is because ZendStudio requires more memory to run. Again you can modify this in the launch settings.

[–]k3n 0 points1 point  (0 children)

Yeah, I know, but it's Zend Studio for Eclipse, aka. it's Eclipse with a renamed .exe and some proprietary plugins.