Hacker News new | ask | show | jobs
by inportb 5141 days ago
> minus Eclipse programming in Java would be a very frustrating experience

I'm not sure about that... Eclipse gets fatter and slower with each release. Of course, I still use it because Google really wants Android developers to do so. In my opinion, the most frustrating thing about using Eclipse for Android work is that it crashes every time I try to export a package, unless I close every open file and restart Eclipse before trying. (the problem is mitigated by disabling automatic builds)

I guess that's because Eclipse runs on Java and Java is wasteful. It would be really nice if we could have a "native" equivalent of Eclipse, with less bloat.
1 comments
why-el 5141 days ago
I face similar issues at work but I don't think Eclipse's issue is Java, else you're saying that anything developed in Java will face a "boated" fate. Eclipse's problem is exactly what Chris mentioned in the article, ok on most things and awesome at none.

Edit: Typos.

link
inportb 5141 days ago
Indeed, it's not all Java's fault. But I think Java does contribute to the overhead because my experience with Java programs in general usually involves long startup time and excessive memory usage.

(And then there's the UI bloat, which makes Eclipse look like this by default: < http://www.flickr.com/photos/geofharries/5145925147/sizes/o/... >. But that's a totally different issue. Thank goodness for Fast View.)

link
why-el 5141 days ago
I see your point there. I myself tolerate Eclipse on Ubuntu, where the UI surprisingly fits, at least for me. Its almost indistinguishable from other UIs, except maybe Spotify which is (IMO) way ahead of the rest. But I cant stand Eclipse on my Mac OS X and there you can see all the stuff you mentioned.
link
lnguyen 5141 days ago
At it's core, Eclipse is really good at Java. It's why it killed off Visual Cafe and most other commercial IDEs (was sad to see Borland go).

The issue is that it's more than just a Java language editor. Once you load it up with all the extras to accommodate development models, frameworks, runtimes, build processes, etc. it does become an unwieldy mess. But it's really hard not to considering how moving parts large-scale development has.

link