Ok but he is wrong though. 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

Ok but he is wrong though. 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.