Yesterday I spent 2 hours just waiting for #EclipseIDE to get its head out of its ass and let me type. Type anything at all. 2 hours of productivity lost. Yay. And thanks, Eclipse!
#EclipseIDE was having a major problem with its auto-complete suggestions for a brand-new, almost empty #java project I just added the day before. It would start churning at me pressing a dot, raise CPU usage to 100%, and never recover.
I tried resetting the auto-complete settings. Tried turning off things I never use. Even raised the amount of memory it could use to 8GB.
Nothing worked.
Thanks, Eclipse.
@aeveltstra Plain text editor, terminal, zsh, compiler & make. That's all you need.
IDEs do nothing but waste resources. It's basically collusion to sell new computers to run IDEs that get slower and need new computers.
@mdhughes @aeveltstra I don't use a IDE, but all i need is not all i want..
Feel my setup could be way better.. Although i must say JEDI is pretty great.
@mdhughes @aeveltstra also use a script that re-runs the last test i edited whenever any file changes which is handy.. Some features i miss:
* In the terminal emulation, can't click or otherwise select files mentioned in (error messages) the output.
Can't in kitty a way to script this in?
* Feel like switching files is more hassle than it should be.. Maybe i am using it wrong. Although unlike emacs, vim can't open a file doubly.
* Much more visualization. For instance graphviz-based.
@jasper @mdhughes @aeveltstra The canonical way to do this in vim is to populate the quickfix list with the error messages, which jumps to any already open buffer for that file https://vim-jp.org/vimdoc-en/quickfix.html
