3 ms·
All that parsing and rendering can be done in the background, not grinding the UI to a halt. As soon as I strike a key on my keyboard, the letter should appear.
by function_seven 4y ago
All that parsing and rendering can be done in the background, not grinding the UI to a halt. As soon as I strike a key on my keyboard, the letter should appear. Instantly. (Ok, in 20ms or 40ms or whatever)
If I'm actively editing a markdown file, I do not need for it to fire off a re-render on each keystroke. It can wait 500ms before starting to do it, and cancel if I hit another key in the meantime. If I start typing after it has started rendering, then go ahead and finish that cycle while still showing me what I type in real time.
However these events are scheduled, the appearance of my typed characters on the screen is going to always be the priority. There's no reason to block UI while doing this.
- WalterBright 4y agoI use Thunderbird mail. It often freezes for several seconds while typing text. This is ordinary behavior for modern software. I'm not excusing it, it's just that it's hardly exclusive to Microsoft. TB is a multithreaded program, but it isn't very good at using it effectively. I've learned through bitter experience to not touch a key or the mouse when it is getting messages.