3 ms·
> It’s hilarious how the same people that talk shit about VSCode being too slow use IntelliJ instead I use VSCode on par with IntelliJ and Clion and I wouldn't
by fivea 5y ago
> It’s hilarious how the same people that talk shit about VSCode being too slow use IntelliJ instead
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?