4 ms·
Honestly for editors like Code or Atom, working with large files or huge XML is more of a niche feature. What I care about in editor performance is responsivene
by revelation 10y ago
Honestly for editors like Code or Atom, working with large files or huge XML is more of a niche feature. What I care about in editor performance is responsiveness, entering characters and having them show up correctly colored on the display. Or navigating with keyboard shortcuts.
Unfortunately this doesn't measure this basic "redraw" performance.
- MichaelGG 10y agoVSCode on an Xubuntu 16 VM (VMWare Workstation on Windows 8.1) on a 5th gen i5 with lots of RAM seems very slow to draw. Even the menus are visibly slow. I was disappointed as I thought this might be a quick and easy way to get vim bindings + Rust editing. Maximized, it's even worse - typing is very slow. But that's apparently some sort of bug.
- tills13 10y agoSimilar hardware (not running in a VM), none of the performance issues you mention here...
- steveklabnik 10y agoI use this setup on a Windows machine, not a VM. Works very fine here.
- satysin 10y agoSounds more like an issue with h/w acceleration used by Electron when running in a VM.
- keithnz 10y agosame, I'm happy to have multiple editors available for different tasks, use code to code a bunch of things, I'd start worrying if I had HUGE files. big files I rarely need to open in an editor, often I just need to extract something out, in which case I use grep.