4 ms·
The only time I've ever used Eclipse was when it was mandated by my employer. That happened to me twice. I didn't stay long at either place - for some reason
by jcadam 6y ago
The only time I've ever used Eclipse was when it was mandated by my employer. That happened to me twice.
I didn't stay long at either place - for some reason both companies were horrible places to work.
I have noticed a lot of new grads come out of College knowing Eclipse (and only Eclipse). Which is probably why it persists - and I still have to deal with it when I have to help junior devs figure out what's wrong with their eclipse config. Occasionally I can get one to convert to IntelliJ - the rest won't try a new IDE and that's a pretty good indicator of what kind of engineer they're going to be :)
- touisteur 6y agoWhat if I tried both and find eclipse far more efficient, more to the point, and I have built muscle memory and feel intellij slows me down... Am I that 'kind of engineer'? The tool is fine and works. Especially the barebones 'just plain java please no fucking plugins I'll handle git in terminal and C/C++ in Vim THANKS'. I understand the annoyance with not being able to fix one's setup and that's on them. But it seems very strange to fixate on what other people use as tools... Especially when both propositions are on the same productivity level. It's not like your colleagues are coding java in vim (and even then if productive AF, why does it bother anyone?).
- jcadam 6y agoI'll clarify: I'm specifically talking about junior devs who are having a lot of trouble with their IDE, have no experience with anything else, and aren't willing to give any other options a shot. It shows a lack of curiosity and/or desire to explore new tools. Some of them don't even know how to do a build outside of Eclipse (worse, I've known some "senior" devs with the same problem). I know one good senior dev who prefers Eclipse. I'm not sure why, but he doesn't seem to have any major issues with it, and he's good, so... ok.