How VSCode made bracket pair colorization 10,000x faster

Re:How VSCode made bracket pair colorization 10,000x faster by wenc on Thursday June 22, 2023 @12:21PM (#36434522)

I used to run vim and VS Code on a Core 2 Duo from 2005. Vim is a lot faster but VS Code is so much more powerful — it’s a full featured IDE. It’s not a quick and dirty text editor like Kate. It’s not meant to be that. I still use vim to edit config files but for everything else I use VS Code.

I’ve since upgraded to a 2014 i7 and now VS Code feels fast.

[ Parent | on HN ]

Re:How VSCode made bracket pair colorization 10,000x faster by CalChris on Thursday June 22, 2023 @12:56PM (#36435177)

I use VSCode NeoVim and clangd. This has gotten so good, although command mode took awhile, that I rarely need to use a terminal vim.

[ Parent | on HN ]

Re:How VSCode made bracket pair colorization 10,000x faster by ColonelPhantom on Saturday June 24, 2023 @06:07AM (#36457268)

Kate is not a "quick and dirty text editor" either? Kate has session and project support (admittedly a bit more clunky than VSCode, but it works), good LSP support, decent built-in search, GDB integration, a built-in terminal, Git integration, etc. Sure, it may be less polished than VSCode in some of these aspects, but they're there and mostly just work.

[ Parent | on HN ]