3 ms·
Still slower than Sublime Text. I gave VSCode a try and this is the reason I went back to Sublime Text. I already have a ST3 license so I didn't care about "fre
by GuB-42 6y ago
Still slower than Sublime Text. I gave VSCode a try and this is the reason I went back to Sublime Text. I already have a ST3 license so I didn't care about "free". Feature wise and community wise they are both very good, with maybe a small advantage for VSCode.
It isn't slow but it has noticeable micro stuttering. Enough to be annoying when coming from an editor that doesn't have this problem.
EDIT: Emacs feels surprisingly slow for such an old software, though not in the same way as VSCode. Vim is fast but I never really got into it.
- drew-y 6y agoI was actually a Sublime Text user before VSCode. I'll be the first to admit Sublime Text is faster. VSCode still wins for me in a landslide. Sublime text's performance is just not enough of an advantage over VSCode's feature set and extension marketplace. VSCode is free as in freedom, which is pretty important to me for a tool that I completely rely on for work. Edit: I'll also add that I've never found VSCode's performance to be a problem. It's pretty rare for me to find a file that's big enough to make VSCode choke. I suppose it might happen with multi-gigabyte log files. But usually I just use journalctl to browse those.
- ahelwer 6y agoEasy way to make vscode choke: hold down ctrl+alt+up/down to enable multi-line editing. Let the cursor run up or down the screen for a bit. It lags a lot. This might be because of the vsvim plugin though, itself the source of a lot of lag.
- drew-y 6y agoYeah that's very odd. I use that feature a lot and have never had it choke. But I also don't use vsvim.