Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
21–30 of 53 posts
Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#22Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#23And I don't even like Java.
Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#24Anybody 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…
Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#25Earlier 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.
Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#26Earlier 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".
Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#27I have been meaning to check out eclim: http://eclim.sourceforge.net/
Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#28Re: Ask HN: Reasonable Java editor for heavily CLI-oriented UNIX types who hate bloat?
#29Emacs? 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.
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?
#30Earlier 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...?