4 ms·

sigh couldn't come at a more appropriate time for me. Alas, isn't these three contradictory: * Use as little software as possible. * Use software that does on

by maayank 15y ago

sigh couldn't come at a more appropriate time for me. Alas, isn't these three contradictory: * Use as little software as possible. * Use software that does one thing well. * Do not use software that does many things poorly. I have a "good enough" workstation with 4GB of memory. No matter how much tweaking I do to eclipse.ini, Eclipse still crawls to an halt when I work on our large Java project... Alas, I can't just change it to VIM + command line svn. It would be a mess.

Derbasti 15y ago
I don't think they contradict. But they seem to imply * Use as few workflows/tasks/'things' as possible.
Derbasti 15y ago
What is holding you back on Vim + command line?
- maayank 15y ago
  well, we run many tests using junit and testNG. my team and our partners also use eclipse so some use maven. And, while it's not Vim's "fault", I'm afraid relearning how to do all my processes (compiling and testing java, running tests and see their results, committing rapidly, etc.) would prove lengthy in a period where I don't have much "free" time.
  - leftnode 15y ago
    I used to have the same fear about Linux, command line, vim, etc. You sound competent, I suspect the learning curve will be a lot less than you fear it will be.
Tyrannosaurs 15y ago
They're not contradictory though I see how you could read them that way. My reading of what he's saying with the three points is: * Don't just go installing and using a bunch of stuff for the sake of it. Make everything justify it's existence on your machine and in your processes. * Multiple individual tools which do things well are better than general tools which do many things badly. Probably also worth distinguishing between amount of software and number of applications. For instance, Eclipse may be just one application but it's a lot of software. It is admittedly a slightly abstract measurement but I think there would generally be broad agreement on the scale of most things. In terms of your specific issue, it may be that 4Gb is not good enough as much as you'd like it to be. It will depend what else you're running, how big the project is, what it's doing and so on... Plus, Eclipse is a pretty chunky tool itself.
stayjin 15y ago
There is a way to use ramdisk as your workspace which makes eclipse quite fast. Check a post at the Scala forum ( I am sorry, do not have the link handy right now )
- maayank 15y ago
  what a brilliant idea. I'll try it first thing Wednesday (it's holiday here in Israel). For future reference, while I didn't find a Scala forum post, I found the following (perhaps you referred to the first item): http://blog.normation.com/2010/07/27/set-up-eclipse-workspace-in-ram/ http://blog.normation.com/2010/07/27/set-up-eclipse-workspac... http://stackoverflow.com/questions/501718/can-i-use-a-ram-disk-to-speed-up-my-ide http://stackoverflow.com/questions/501718/can-i-use-a-ram-di... http://stackoverflow.com/questions/1838018/optimize-use-of-ramdisk-for-eclipse-development http://stackoverflow.com/questions/1838018/optimize-use-of-r...
  - stayjin 15y ago
    Yes, that was the one I was referring to. Thanks for citing the links.

by maayank 15y ago

Derbasti 15y ago

I don't think they contradict. But they seem to imply * Use as few workflows/tasks/'things' as possible.

Derbasti 15y ago

What is holding you back on Vim + command line?

maayank 15y ago
well, we run many tests using junit and testNG. my team and our partners also use eclipse so some use maven. And, while it's not Vim's "fault", I'm afraid relearning how to do all my processes (compiling and testing java, running tests and see their results, committing rapidly, etc.) would prove lengthy in a period where I don't have much "free" time.
- leftnode 15y ago
  I used to have the same fear about Linux, command line, vim, etc. You sound competent, I suspect the learning curve will be a lot less than you fear it will be.

Tyrannosaurs 15y ago

They're not contradictory though I see how you could read them that way. My reading of what he's saying with the three points is: * Don't just go installing and using a bunch of stuff for the sake of it. Make everything justify it's existence on your machine and in your processes. * Multiple individual tools which do things well are better than general tools which do many things badly. Probably also worth distinguishing between amount of software and number of applications. For instance, Eclipse may be just one application but it's a lot of software. It is admittedly a slightly abstract measurement but I think there would generally be broad agreement on the scale of most things. In terms of your specific issue, it may be that 4Gb is not good enough as much as you'd like it to be. It will depend what else you're running, how big the project is, what it's doing and so on... Plus, Eclipse is a pretty chunky tool itself.

stayjin 15y ago

There is a way to use ramdisk as your workspace which makes eclipse quite fast. Check a post at the Scala forum ( I am sorry, do not have the link handy right now )

maayank 15y ago
what a brilliant idea. I'll try it first thing Wednesday (it's holiday here in Israel). For future reference, while I didn't find a Scala forum post, I found the following (perhaps you referred to the first item): http://blog.normation.com/2010/07/27/set-up-eclipse-workspace-in-ram/ http://blog.normation.com/2010/07/27/set-up-eclipse-workspac... http://stackoverflow.com/questions/501718/can-i-use-a-ram-disk-to-speed-up-my-ide http://stackoverflow.com/questions/501718/can-i-use-a-ram-di... http://stackoverflow.com/questions/1838018/optimize-use-of-ramdisk-for-eclipse-development http://stackoverflow.com/questions/1838018/optimize-use-of-r...
- stayjin 15y ago
  Yes, that was the one I was referring to. Thanks for citing the links.