3 ms·
> I can open stupidly large files and not worry, or mash page down and have no lag. In my experience, vim tends to start choking on files in the 100MB/1GB rang
by jcranmer 6y ago
> I can open stupidly large files and not worry, or mash page down and have no lag.
In my experience, vim tends to start choking on files in the 100MB/1GB range.
- robotmay 6y agoHaha yeah that's probably close to my experience too. But I wouldn't even dare try in other editors. My experience with vim always seems atypical when I read blog posts like this. For me it's a hard-to-kill, reliable text editor. I barely know any of the commands (despite using it for a decade) because I've honestly never felt like I was missing anything. Just having something reliably fast lets me get away with inefficiencies that are problems elsewhere. I can't stand hjkl navigation, or remember anything more complex than how to find/replace strings. But I'm perfectly happy with it just like that.
- tutfbhuf 6y agoFor files that big I often find myself switch back to vi. However, vi also has its limits. If the files are really huge, then grep, head, tail and awk are my best friends.