4 ms·
It's not unbearable, I've done a huge amount of Java coding on the command-line. Yes, it's harder, but I strongly believe it's better to move onto Eclipse only
by ZoFreX 14y ago
It's not unbearable, I've done a huge amount of Java coding on the command-line. Yes, it's harder, but I strongly believe it's better to move onto Eclipse only after learning how the tools actually work underneath. It makes it far easier to debug weird issues with the IDE, and means you're not SOL if the IDE breaks, or you're on another person's computer - you're just a bit slower, and I'd argue that applies to all tools (custom aliases, bash scripts, vim config) and not just IDEs.
- kaffiene 14y agoSimilar story. I used to do everything with Emacs. Java IDEs were able to offer more value and make me move from my standard dev environment (I have a C, C++, LISP background). The Java standard libraries are so numerous that having something to remember the names and parameters of all those methods is a huge win. I don't see how you can see this as a weakness of Java - if it were so bad, you wouldn't have so many languages launched on the JVM to take advantage of the Library ecosystem.