I guess the MacBook Pro's days are numbered, then?
I guess stability, tooling ecosystem, and ages of user/customer support info means nothing then, and being new is reason enough to scrap all your tooling and workflow?
Developers are paid to deliver features, and test-driving the latest and greatest fad gets in the way.
The big thing about VSCode that I really like is that it just seems to be easier to look at... There's less visual cruft by default than in IntelliJ.
Edit: Not to say that I'm right or that you're wrong. Just pointing out differing opinions exist. To each their own.
VSCode shines in comparison only when all you need is a text editor to quickly open a couple of files, you don't need to do anything beyond reading code without navigating files or doing the occasional typo fix, and you don't actually need an integrated development environment.
Other than that, I struggle to come up with a scenario where, if anyone already had both installed, vscode would be the preferred solution.
My IJ is set up in a way that it is very clean. Tabs, file explorer, editor, embedded terminal if needed. It doesn't get much cleaner.
I use VSCode on par with IntelliJ and Clion and I wouldn't put VSCode ahead in the performance department. In fact, until a few months ago VSCode suffered from a rather eggregious performance problem caused by the pathological way that intellisense scanned files that rendered it unusable with some projects. We're talking about full blown hangs which led to forced restarts. In fact, I find the jab quite funny because IntelliJ's main performance issues are also tied to file indexing, but here I see vscode being portrayed as behaving better?
Both IntelliJ and vscode are great at what they do, and their main usability issues stem from the same type of feature/problem. Why try to one-up either of them?