2 ms·

I'll just keep using Eclipse over here in the corner :-) I guess its a case of sunk investment, but having got to the point of understanding top to bottom how

by zmmmmm 6y ago

I'll just keep using Eclipse over here in the corner :-) I guess its a case of sunk investment, but having got to the point of understanding top to bottom how Eclipse works I find that it still beats everything else in terms of presenting me with a completely comprehensive framework for developing at a high level of complexity across multiple languages and environments. Every time I move to another tool I find them better on the surface but missing these deeper features that enable dealing with super complex infrastructure across many projects in many languages.

fctorial 6y ago
> missing these deeper features examples?
- zmmmmm 6y ago
  A lot is in the framework level features: I have workspaces set up with combinations of projects configured as dependencies for each other. The perspectives feature allows me to then have specific window configurations for each, and the working sets lets me zero in on a particular subset of projects and files for what I'm working on. The incremental compilation that crosses project boundaries then means I can, for example, jump into something in library, refactor it, immediately (like, less than a second) have all the errors across all the projects across multiple languages show up from this change ... and nearly as easily execute all the unit tests. I have projects where pieces are written in PHP, python, Java, Groovy and Javascript and these can all be open at once and do things like, set breakpoints in each step of a flow that executes across them all and follow a process end to end to inspect where it is going wrong. It may well be this is somehow all possible in IntelliJ but the times I have tried it out I couldn't work out how to do anything as sophisticated as what I routinely do in Eclipse. It could barely highlight the errors in one project correctly without launching Gradle, let alone propagate that downstream to all the dependencies.
dhosek 6y ago
I used to be an Eclipse zealot. I clung to it even as my co-workers moved to IntelliJ. When I finally made the jump, I found it a huge boost to productivity and stability. I needed for a while on one project to run Eclipse to be able to use an IBM plugin for their rules engine and it was painful how much slower and crash-prone Eclipse was.

by zmmmmm 6y ago

fctorial 6y ago

> missing these deeper features examples?

zmmmmm 6y ago
A lot is in the framework level features: I have workspaces set up with combinations of projects configured as dependencies for each other. The perspectives feature allows me to then have specific window configurations for each, and the working sets lets me zero in on a particular subset of projects and files for what I'm working on. The incremental compilation that crosses project boundaries then means I can, for example, jump into something in library, refactor it, immediately (like, less than a second) have all the errors across all the projects across multiple languages show up from this change ... and nearly as easily execute all the unit tests. I have projects where pieces are written in PHP, python, Java, Groovy and Javascript and these can all be open at once and do things like, set breakpoints in each step of a flow that executes across them all and follow a process end to end to inspect where it is going wrong. It may well be this is somehow all possible in IntelliJ but the times I have tried it out I couldn't work out how to do anything as sophisticated as what I routinely do in Eclipse. It could barely highlight the errors in one project correctly without launching Gradle, let alone propagate that downstream to all the dependencies.

dhosek 6y ago

I used to be an Eclipse zealot. I clung to it even as my co-workers moved to IntelliJ. When I finally made the jump, I found it a huge boost to productivity and stability. I needed for a while on one project to run Eclipse to be able to use an IBM plugin for their rules engine and it was painful how much slower and crash-prone Eclipse was.