And it's not even like he ignores the advantages since he uses IntelliJ for Java!
Emacs users believe the tool should be adapted to the user rather than the user adapting to the tool.
I don't know what to say. Ignorance and antagonism mixed together, consciously...
... Maybe emacs users know something you don't?
(FWIW I have been using JetBrains tools' & emacs as well for over a couple decades now [since IntelliJ 3-something back in 2003 if I recall], usually complimentary to each other, not competing. As of last week, I am not renewing my CLion subscription, and work fully in emacs and it's fine.)
* Buffer and frame management. Getting used to splits and quickly bouncing between buffers is something that is a muscle memory, at this point.
* Pretty much complete introspection of the editor. All of the help functions, as well as the *Messages* buffer are things that are often very hidden in other editors.
* The "all is fair" community. There are some grumpy style folks that use it, of course. I've found that most are far more friendly and open to you doing things however you want than in most other communities. The pedantic nature of a lot of developers falls over into a lot of our entire industry, it is refreshing to find a community that is pragmatic over pedantic to this level.Though actually I'm not sure if they'll do it on directory name components or just the filename itself.
They will, however, have 5x the memory and battery consumption and not be nearly as snappy in response time, nor nearly as customizable.
a) he's wrong to call it outdated... because that's not the case, it's a very vibrant community and with boatloads of dev happening
b) he's wrong to say it only does 10% of blah blah blah -- capability wise my config does pretty much everything I had with CLion/RustRover in terms of my C++/Rust workflow... but also a whole lot more on other fronts
c) he's wrong to formulate a comment like that because it's inflammatory and not nice
Honestly, futzing with VSCode is pretty much as 'brittle' and 'batteries not included' situation as emacs, though obviously more popular. Every time I went from CLion over to VSCode I just threw my hands up in annoyance.
My emacs + lsp + company + rust-analyzer + projectile + treemacs setup works better for me, though obviously that's somewhat because I have 30 years of mild-muscle-memory for emacs keybindings. (Though there is cua-mode, y'know)
Would I recommend it for brand new devs, or for my 13-year old son starting out or something? Probably not. But it's really none of my business what tools other people use.
From then on, the experience feels pretty modern, while remaining infinitely customizeable in a structured way.
Most modern IDEs even come with key mappings for emacs so you can switch instantly and leverage their superior feature set without having to relearn anything.