Back when I was working on the VS editor team, we had to worry about things like users opening multiple-gigabyte XML files in the editor, expecting text to immediately display, and for the little scroll nubbie to immediately size to the correct proportional size (the size of the nub is proportional to the number of lines displayed in the window versus the overall number of lines in the file, with some thresholding). And be able to start clicking immediately on the scroll bar, expand/collapse regions, etc.
It's a hard problem that requires pretty serious engineering, especially when your user expectations are that you should be at least as fast as emacs and vim, but also support all of your other features.
And yes, people open large files all the time. Log files; autogenerated "component configuration" babble; registry text dumps; debugging diagnostic output...
It's a hard problem that requires pretty serious engineering, especially when your user expectations are that you should be at least as fast as emacs and vim, but also support all of your other features.
And yes, people open large files all the time. Log files; autogenerated "component configuration" babble; registry text dumps; debugging diagnostic output...