|
|
|
|
|
|
by Swizec
3027 days ago
|
|
|
vim is for when you want to edit anything in the console. Git commit? Vim. Quickly edit a config file? Vim. SSH'd into a server and need to check something? Vim. Day to day coding ... VS Code. Used to be Emacs, but I switched. Oh and Vim is still the only editor I dare use to open a 1GB CSV file with. |
|
|
vim isn’t actually even so good at this. It still needs to read the whole file into memory. Yes, it doesn’t need to syntax-highlight the whole file, but it does still need to keep it in memory.
Other editors work by just loading enough of a big file to keep the illusion up that they have loaded all of it, when they are in fact dynamically loading and unloading parts as the user navigates within the file.
I think sublime works like that, though it still does something that requires load time proportional to the file length.
Many hex editors also do this, probably out of necessity because they are often used to inspect huge binary files (like disk images), though thanks to never having to do line wrapping, they also have it much easier to do so.