3 ms·

Since you mention IntelliJ, is it possible that the corporations you have worked in have been heavy on Java? JDEE (http://jdee.sourceforge.net/ http://jdee.sou

Since you mention IntelliJ, is it possible that the corporations you have worked in have been heavy on Java? JDEE (http://jdee.sourceforge.net/ http://jdee.sourceforge.net/) exists, but even I give up on Emacs when I want to write a lot of Java (and I use Emacs for literally everything else, including JS).

schwartzworld 6y ago
JS development in IntelliJ/WebStorm is an amazing experience. The refactoring features alone make it easy to write code without worrying about details like "where does the file go" or "what should I name this". You can get the code working and rename / move code with a single click later on, knowing the refactor will propagate through the app. The intellisense is amazing too. Start typing a method name and you see arguments with type annotations. it's overkill for scripting, but working on tangled legacy code it's very helpful.
- xapata 6y ago
  I've heard people say that, but what I find is that they pick shitty names and never refactor. I'm on a different team now. Most of us use vim.
  - schwartzworld 6y ago
    Yeah, but then when someone tells you in code review to pick a less shitty variable name, it still takes one click.
    - xapata 6y ago
      Sadly, when you get a reputation for giving that feedback, people stop asking you to review.
      - schwartzworld 6y ago
        Damn. You must work on a shitty team.
        xapata 6y ago
        I'm on a different team now.
User23 6y ago
I wouldn’t write Java in an editor that wasn’t hosted in the JVM. The advantages are simply too great. On the other hand that’s a very Lispy attitude so Emacs still influences me. And Eclipse at least has tolerable Emacs style bindings available. Still it sucks how much more of a PITA it is to create an Eclipse plug-in than to just write a page or two of elisp.
elevader 6y ago
I don't do a lot of java development but https://github.com/emacs-lsp/lsp-java https://github.com/emacs-lsp/lsp-java works really well for me.

schwartzworld 6y ago

JS development in IntelliJ/WebStorm is an amazing experience. The refactoring features alone make it easy to write code without worrying about details like "where does the file go" or "what should I name this". You can get the code working and rename / move code with a single click later on, knowing the refactor will propagate through the app. The intellisense is amazing too. Start typing a method name and you see arguments with type annotations. it's overkill for scripting, but working on tangled legacy code it's very helpful.

xapata 6y ago
I've heard people say that, but what I find is that they pick shitty names and never refactor. I'm on a different team now. Most of us use vim.
- schwartzworld 6y ago
  Yeah, but then when someone tells you in code review to pick a less shitty variable name, it still takes one click.
  - xapata 6y ago
    Sadly, when you get a reputation for giving that feedback, people stop asking you to review.
    - schwartzworld 6y ago
      Damn. You must work on a shitty team.
      - xapata 6y ago
        I'm on a different team now.

User23 6y ago

I wouldn’t write Java in an editor that wasn’t hosted in the JVM. The advantages are simply too great. On the other hand that’s a very Lispy attitude so Emacs still influences me. And Eclipse at least has tolerable Emacs style bindings available. Still it sucks how much more of a PITA it is to create an Eclipse plug-in than to just write a page or two of elisp.

elevader 6y ago

I don't do a lot of java development but https://github.com/emacs-lsp/lsp-java https://github.com/emacs-lsp/lsp-java works really well for me.