4 ms·

Eclipse teaches developers so many bad habits that I will be quite happy for it to die in the fire.

by spiralpolitik 11y ago

ljk 11y ago
been using eclipse since in school so never thought about it, but what are the bad habits?
- deleted 11y ago
  [deleted]
- spiralpolitik 11y ago
  Two examples: - Dependencies between modules in the same source base for one, which given the most common setup (single workspace) Eclipse will quite happily ignore and treat everything as one module. - The default static analysis setup misses so many common things (unused imports, methods, variables) that whenever I open a class in IntelliJ I have to spend 5 minutes removing the cruft. In its time Eclipse was a good IDE, but its time has passed.
  - Karunamon 11y ago
    That second one confuses me, Eclipse as of the three days ago I last opened it absolutely does warn about unused imports, methods, and variables. And this is with the bog standard out of the box configuration.
  - anthonybsd 11y ago
    > Dependencies between modules in the same source base for one, which given the most common setup (single workspace) Eclipse will quite happily ignore and treat everything as one module. Wait what? I have no idea what you are talking about. If modules are depending upon each other via Maven, you simply stick dependant one to the other's classpath if you want to use the workspace version. > The default static analysis setup misses so many common things (unused imports, methods, variables) that whenever I open a class in IntelliJ I have to spend 5 minutes removing the cruft. I'm looking at the same project here side by side and once again I'm not sure what you are referring to. If anything, some of IntelliJ assumptions for code quality can actually result in more fragile code if you aren't careful.
  - mindcrime 11y ago
    The default static analysis setup misses so many common things (unused imports, methods, variables) that whenever I open a class in IntelliJ I have to spend 5 minutes removing the cruft. That does not jibe with my experience with Eclipse at all. I see the stock configuration being quite comprehensive in showing those kinds of warnings, including all three of the items you just mentioned.

Eclipse teaches developers so many bad habits that I will be quite happy for it to die in the fire.

ljk 11y ago

been using eclipse since in school so never thought about it, but what are the bad habits?

deleted 11y ago
[deleted]
spiralpolitik 11y ago
Two examples: - Dependencies between modules in the same source base for one, which given the most common setup (single workspace) Eclipse will quite happily ignore and treat everything as one module. - The default static analysis setup misses so many common things (unused imports, methods, variables) that whenever I open a class in IntelliJ I have to spend 5 minutes removing the cruft. In its time Eclipse was a good IDE, but its time has passed.
- Karunamon 11y ago
  That second one confuses me, Eclipse as of the three days ago I last opened it absolutely does warn about unused imports, methods, and variables. And this is with the bog standard out of the box configuration.
- anthonybsd 11y ago
  > Dependencies between modules in the same source base for one, which given the most common setup (single workspace) Eclipse will quite happily ignore and treat everything as one module. Wait what? I have no idea what you are talking about. If modules are depending upon each other via Maven, you simply stick dependant one to the other's classpath if you want to use the workspace version. > The default static analysis setup misses so many common things (unused imports, methods, variables) that whenever I open a class in IntelliJ I have to spend 5 minutes removing the cruft. I'm looking at the same project here side by side and once again I'm not sure what you are referring to. If anything, some of IntelliJ assumptions for code quality can actually result in more fragile code if you aren't careful.
- mindcrime 11y ago
  The default static analysis setup misses so many common things (unused imports, methods, variables) that whenever I open a class in IntelliJ I have to spend 5 minutes removing the cruft. That does not jibe with my experience with Eclipse at all. I see the stock configuration being quite comprehensive in showing those kinds of warnings, including all three of the items you just mentioned.