Live data from Hacker News

Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?

news.ycombinator.com

21–30 of 53 posts

Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?

#23
The pain of Eclipse's bloat is real, but the speed with which you can learn new libraries through its features is worth it. I won't come within 10 feet of Eclipse for anything but Java, but its so great it makes Java fun because I can effortlessly zoom through definitions in multiple layers of libraries and figure out what is going on faster than in any other language/IDE.

And I don't even like Java.

Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?

#24
post #15

Anybody who writes java code in anything outside of Eclipse, NetBeans or IntelliJ is wasting their time. It doesn't take an enormous amount of time to learn how to use Eclipse. It probably takes 15 minutes of someone showing you the ropes. You need to stop thinking of the problem as "I need a text editor" because that's almost certainly not what you need. Eclipse in particular does nothing like what you claim ("unnec…

I'm the complete opposite of the OP. My intro CS courses were taught using Eclipse, and I am constantly using it (for lack of a better, free, option) at work. I am getting more and more fed up with the bloat in Eclipse. Running in a Linux environment results in hard-to-diagnose crashes fairly often, and the memory overhead is, quite frankly, unacceptable. I would gladly move to something lightweight like the OP asked…

That's what I'm saying.

Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?

#25

Earlier quoted context omitted.

How do I export the project back out to its original form once I imported it into the workspace? Or is it safe to just copy the stuff out of my workspace folder?

First of all: you are using version control, right? Please tell me yes. Eclipse isn't going to "change" your code at all. It'll put two or three files and dirs in the root of your project. That's it. Your code is the same as it was before.

Yep, using SVN. Not sure I want Eclipse to ride it, though.

Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?

#26
post #18

Earlier quoted context omitted.

How do I export the project back out to its original form once I imported it into the workspace? Or is it safe to just copy the stuff out of my workspace folder?

Eclipse won't change your file/folder structure (unless you tell it to). In fact, you can have source code somewhere outside of your "workspace" and just point Eclipse to it, there is no requirement for the code to be inside the "workspace".

I'm guessing that's done by some method other than the "Import" facility...?

Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?

#29
post #2

Emacs? For command-line folk, either Emacs or vi would probably make the most sense long-term. They often have plugins to add functionality to make them more IDE-like. Learning curve's a bit tougher though, and might require more effort than it's worth. I still haven't completely switched over to Emacs yet, but it might pay off in the long run.

I used emacs for everything and relatively recently got into the situation of having to do some java.

http://jdee.sourceforge.net/

It handles that too. I like having one editor that can follow me everywhere. Maybe Eclipse or the others work better for java or more out of the box or some such thing, but to me there's a huge benefit to having my programming editing behaviors consistent in a terminal, my desktop, PHP, perl, C, C++, java, etc. (with mode/language specific enhancements of course).

If I grew up on Eclipse I'd probably feel the same way I suppose about it.

Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?

#30
post #18

Earlier quoted context omitted.

Eclipse won't change your file/folder structure (unless you tell it to). In fact, you can have source code somewhere outside of your "workspace" and just point Eclipse to it, there is no requirement for the code to be inside the "workspace".

I'm guessing that's done by some method other than the "Import" facility...?

Import will just tell Eclipse where the code is located, not actually copy it into the workspace. Import is probably what you want.
Post reply on HN