4 ms·
Unless you know what you are doing, a heavily configured vim can be really slow. It can approach a level of slowness comparable to atom at times. If you have t
by EduardoBautista 9y ago
Unless you know what you are doing, a heavily configured vim can be really slow. It can approach a level of slowness comparable to atom at times. If you have to heavily configure vim to get it to a point that it's useful for your workflow, I highly recommend giving sublime a try, it has truly made writing code more enjoyable for me.
- anon335dtzbvc 9y agoWell modern plugin managers have lazy plugin loading based on the current filetype. You open .cpp vim transforms into a cpp "ide". You open .hs ghc-mod and friends has you covered. Lazy plugin solved the old problem of having hundred vim plugins loaded at the same time resulting in an slow ide like experience.
- nerdponx 9y agoI stopped having performance problems when I switched to NeoVim.
- reificator 9y agoMoved from Sublime to VS Code for font ligature support. (I like Fira Code) Stayed for: * Integrated terminal that also supports ligatures * Pluggable debugger: one interface across gdb, delve, node, Chrome and other browsers, etc... * Built in git support that's nicer in my opinion than any of the plugins for Sublime * Markdown previews * Seriously good Intellisense, it even tells me the schema of nested objects returned from another function in JavaScript. * Probably some more that I forgot... I don't regret buying Sublime, but VS Code targets the same platforms, has way more features and a faster release cycle, and did I mention it's free and open source?
- deleted 9y ago[deleted]
- jrs95 9y agoPersonally I've had Sublime approach near Atom levels of slowness from plugins as well. I'd imagine it depends on the plugins, but that's essentially what slows any of these editors down a lot. For what it's worth, I always use Sublime for really large files.