▲ | CharlesW 2 days ago | |||||||
Googling around a bit, Sublime Text doesn't seem to be particularly good at this: https://forum.sublimetext.com/t/unable-to-open-a-large-text-... In my experience, BBEdit will open files that kill other editors: "Handling large files presents no intrinsic problems for BBEdit, though some specific operations may be limited when dealing with files over 2GB in size." | ||||||||
▲ | roto 2 days ago | parent | next [-] | |||||||
I have always found sublime to be the best at large files, well over 1gb. Since you mention bbedit, maybe this is some mac specific issue? I really don't know. But at least among people i know, opening large files has effectively become its main USP. Should be noted that the linked post is almost 15 years old at this point too, so perhaps not the most up to date either. | ||||||||
▲ | xrisk 2 days ago | parent | prev | next [-] | |||||||
While I don’t know if the claim is true, you’ve linked a post from 2012… | ||||||||
▲ | spartanatreyu 2 days ago | parent | prev [-] | |||||||
Sublime text works better on large files (where file sizes are a few gb) compared to VSCode. But, you can go faster depending on your usecase: - If you're trying to manually look through the file, use `less`. You can scroll up and down, go quickly to the top and bottom of the file, and also search the file for strings quickly - If you already know the string in the file that you're looking for, use ripgrep - If you're trying to do a search and replace, and you already know what the strings are, use sed. (macos' built-in sed isn't good, so get the proper gnu coreutills through homebrew, and you can access the good sed through `gsed`) | ||||||||
|