I use IntelliJ for Java. There's nothing to touch it. What bugs me is that every year or so they change things around and you have to figure out how everything works again, or they discontinued support for a plugin for a particular version of a VCS you were using ... (no I'm not bitter ;)
But I use Emacs for everything else. Emacs never changes how things are done. It can't do Java the way I'm used to doing it though. It took me a whole heap of work to get competency to a level I was actually productive with though, so I can appreciate why it's a tough sell. Worth it though IMO. Though I pity the person who has to pair program with me!
Re:Editor Overload
by JackMorgan on Friday August 28, 2020 @08:07AM
(#24303882)
If you're interested in learning Vim, I wrote up a bunch of practice exercises for every command to build muscle memory. They are intended to only take about 10 minutes a day for a couple weeks to help learn specific commands. Here's a few free sample chapters: https://github.com/steveshogren/10-minute-vim-exercises/blob...
Re:Editor Overload
by square_usual on Friday August 28, 2020 @06:04AM
(#24303187)
I have the same setup with Sublime instead of VS Code. Sublime starts faster and takes up less memory, and I don't need the things vsc is better at for my scratchpad needs. For when I don't want to use a JetBrains IDE I just use code full stop.
Re:Editor Overload
by closeparen on Friday August 28, 2020 @01:11PM
(#24307351)
I’m hoping beyond hope that Jetbrains one day implements a client-server architecture. The codebase at work is getting too big for our MacBooks to reasonably “git pull,” build, and index. The solution on offer is very powerful cloud instances. The only GUI editor option there is VSCode. It’s okay, but nowhere near Jetbrains level.
Me and Vim never clicked. Mind you that may also be because I've not found a good tutorial / practice thing yet, nothing that stuck or that pushed me to get the various commands into my muscle memory.