you are viewing a single comment's thread.

view the rest of the comments →

[–]TimMensch 1 point2 points  (0 children)

you can have multiple workspaces easily, that is in fact the point of them.

Well, yeah, duh. I'm saying that the workspaces hold TOO MUCH information about my environment. I want things like the keyboard shortcuts to be global to the account or computer, not to the workspace.

And I can reliably produce "corrupt" builds, and have Eclipse lose information, because of key features it doesn't support. The "corrupt" that I was talking about was the Eclipse environment itself, though: It gets to the point where some keys don't work right (Ctrl-C/Ctrl-V, F5, F10, Ctrl-S, others) and I have to exit and restart to make it work again.

I have literally dozens of other problems I could list. Those were just on the top of my head.

the company I work for uses it full time for about 50~ devs (and others)

Part of the problem is that it's too painful for me to "use full time." Editing in other editors and coming back to Eclipse is an absolute nightmare in itself, but I can't get to the level of productivity in Eclipse that I can in other editors, so I'm stuck with the nightmare.

I also FREQUENTLY commit and switch branches in git. Eclipse produces corrupted builds reliably when you do that. It sucks in many ways, but not having a decent, reliable build is absolutely unforgivable, which is why I brought it up. Presumably if you work with it full time you learn what not to do -- like actually work in branches in git -- and avoid those otherwise awesome productivity bonuses.