3 ms·

Yeah, tried that. Multiple times. IntelliJ just doesn't handle it performance wise, and it feels awkward because IntelliJ just isn't designed as well for workin

by hugi 7y ago

Yeah, tried that. Multiple times. IntelliJ just doesn't handle it performance wise, and it feels awkward because IntelliJ just isn't designed as well for working on multiple projects simultaneously. It's probably great for people working on a single project with some dependencies (modules). IntelliJ really wants you to open a project, work on it, then you close it and open the next project. That doesn't fit me. Doesn't mean IntelliJ is bad, it's just a bit limited in that regard. My dozens of projects are not a single project with "modules". I have a universe of code in multitudes of interrelated projects, closed source and open source. I want to refactor openly, not having to care how I'm moving code between projects. Eclipse works perfectly for this. IntelliJ does not.

AnthonBerg 7y ago
IntelliJ really wants you to open a project, work on it, then you close it and open the next project. That doesn't fit me. This does not match my experience at all, fwiw. I keep all manner of projects open simultaneously.
Aeolun 7y ago
I think it’s interesting that this issue was exactly why I switched away from Eclipse years ago. The performance was atrocious. I guess that pushed them to improve ;)
- hugi 7y ago
  Yeah, "modern Eclipse" is a very different beast from "several years ago Eclipse", that also goes for performance. As I said in a parent, I'm very certain the competition from IntelliJ got them off their asses :).
deanCommie 7y ago
If the project share code that you want to refactor, then in Intellij's terminology they are modules, not projects Import each one individually as a new module in a root project, and everything will be hunky dory. A "module" in this case is just an atomic closure of some sort. I've got plenty of Intellij projects with >50 modules, each of which are their own git repository, just fine.
- hugi 7y ago
  You kind of described the exact problem there. You have "plenty of projects with >50 modules". I don't have "plenty of workspaces", just one that contains all my "plenty of projects", almost all of which then depend in some way on a tree of hierarchies also within that workspace. There are no islands. There's now switching between anything. It's just all my code and dependencies, always open and accessible and instantly available. Creating a new project in Eclipse then requires no importing of modules on my part, I just create a new project, it's in my workspace and voila—it's now an integral part of my universe of code.

by hugi 7y ago

AnthonBerg 7y ago

IntelliJ really wants you to open a project, work on it, then you close it and open the next project. That doesn't fit me. This does not match my experience at all, fwiw. I keep all manner of projects open simultaneously.

Aeolun 7y ago

I think it’s interesting that this issue was exactly why I switched away from Eclipse years ago. The performance was atrocious. I guess that pushed them to improve ;)

hugi 7y ago
Yeah, "modern Eclipse" is a very different beast from "several years ago Eclipse", that also goes for performance. As I said in a parent, I'm very certain the competition from IntelliJ got them off their asses :).

deanCommie 7y ago

If the project share code that you want to refactor, then in Intellij's terminology they are modules, not projects Import each one individually as a new module in a root project, and everything will be hunky dory. A "module" in this case is just an atomic closure of some sort. I've got plenty of Intellij projects with >50 modules, each of which are their own git repository, just fine.

hugi 7y ago
You kind of described the exact problem there. You have "plenty of projects with >50 modules". I don't have "plenty of workspaces", just one that contains all my "plenty of projects", almost all of which then depend in some way on a tree of hierarchies also within that workspace. There are no islands. There's now switching between anything. It's just all my code and dependencies, always open and accessible and instantly available. Creating a new project in Eclipse then requires no importing of modules on my part, I just create a new project, it's in my workspace and voila—it's now an integral part of my universe of code.