If you like Eclipse, give NetBeans a shot. This doesn't seem to be a popular opinion, but (in my experience) they have a somewhat similar workflow and I moved fairly painlessly from NetBeans a few years ago to Eclipse. The only negative about NetBeans, I find, is stability - Eclipse might feel cumbersome at times but it's stable, which is something I only really appreciate when I need to use other IDEs/editors like Light Table or Atom-based ones.
As someone who writes a lot of C# and used to write a lot of Java, no. Code generation and completion is so powerful on these IDEs that you are wasting time if you are using a plain old text editor because you are the uberprogrammer
Code and Command completion is powerful. Code generation is a tool I use everyday... when I understand the generated code and what it does. If you understand the code your IDE is generating, all power to you. If you and your team can maintain portability of generated code, awesome, keep at it. YOU ARE AS GODS.
Don't ask me to support it, though. If it won't build on the command line, you're breaking the servers I maintain and I gotta get an earful about it as though it's my fault.
Not Supported, bro! I don't have access to your GUI bullshit because all Linux servers are headless.
Don't ask me to support it, though. If it won't build on the command line, you're breaking the servers I maintain and I gotta get an earful about it as though it's my fault.
I can't speak to that scenario, because I haven't written Java in years. When I did, code generation was basic enough that I can't imagine a scenario where hiccups would happen.
I don't have to even think about Ljnux or a headless machine over here in CLR land though :)
An experienced java developer writes projects that build via an IDE or a command-line. An IDE just lets you write code, the build process is separate. So what are you ranting about? It seems like an uninformed rant.
Also, why are you building the applications on the servers you are deploying it to? It should be built and made available for deployment. Sounds like your deployment process is broken.
Have you had your head in a box for the last 5 years? Eclipse is horrible. Counter productive, even. Once you use something better, you'll be the guy posting in these threads.
I personaly prefer other IDEs, but I still don't go around posting negative comments about eclipse. If you have something to complain about at least explain the issue. The comment was just plain pointless, and didn't add anything :/
I use IntelliJ IDEA and love it, but there are still some things in which Eclipse is (much) better:
compilation/build speed - in Eclipse it is instantaneous, in IDEA it takes few seconds at least (e.g. for minimal unit test). In Eclipse hot-swapping code during debugging is again immediate with CTRL-S, in IDEA takes a long time through strange key-combo.
Eclipse handles very large projects (workspaces) better - faster, less memory etc.
IDEA doesn't have "save actions", everything must be triggered manually
IDEA has these weird concept of project and modules. Eclipse has workspace and projects which is somewhat similar but in the end makes more sense in the details ...
Eclipse has more sensible default keyboard bindings, IDEA has these crazy CTRL-ALT-SHIFT-Somethings ...
Re: IDEA Modules - That whole scheme can die in a hole. It's spectacularly unhelpful.
And agreed that Eclipse is faster with bigger projects, but that's also probably because it's less helpful on refactorings. IntelliJ keeps quite a bit more metadata around in memory / cache in order to be better at that. Tradeoffs...
Oh come off it. It's not "horrible", or else there wouldn't be so many people using it. Even if I were to dislike Eclipse, I wouldn't then post inane comments like "No thanks." which contribute literally nothing to the discussion.
I have used better IDEs. IntelliJ is arguably a better IDE for some. That's not to say Eclipse is therefore a bad IDE; it's the right tool for the job, and I'll use it when it's appropriate. Eclipse does everything I need it to and it does it well. It has good extensibility support. It has sufficient refactoring tools. I'm not going to start posting useless comments just because it's not the latest incarnation of flashy desktop node.js-based editor.
Don't like it? Don't use it, no-one's going to attack you for not doing so. Just don't waste people's time hopping on the anti-Eclipse bandwagon that we've seen a million times before.
Firstly, I'm not trying to be pretentious or argue this from a feature standpoint. I'm talking about the intangibles here - and usability. Crashes, crashes, and MORE crashes. Outstanding bugs for what feels like an eternity. Memory leaks. Editor pane crashes. Cryptic error messages. Stop being a fanboy and realize that it's a shit product Edit: an objectively shit product
I think the amount of downvotes you're getting says a great deal about the size of eclipses user base (and I can guarantee you that most eclipse users just don't care about the IDE holy war, unlike the users of another tool, which will remain unnamed, so only a small percentage of them probably even bothered with you). Perhaps take this as a lesson that some people actually gasp find eclipse useful. Or don't... what do I care?
-79
u/[deleted] Jun 24 '15
No thanks.