3 ms·
> But for tiny programs that run on your workstation, using 1.3% CPU doesn't cost more than 1% CPU. Especially considering that text editor state changes are d
by throwaway894345 5y ago
> But for tiny programs that run on your workstation, using 1.3% CPU doesn't cost more than 1% CPU.
Especially considering that text editor state changes are dependent on user interaction—it’s not like a video games where the state changes continuously.
- mbreese 5y agoThe focus on framerates isn’t to account for changes as the user is typing, but rather scrolling. When scrolling through text, is it smooth? Does it tear? For me, that’s what I see when a text editor refers to framerates.
- throwaway894345 5y agoEven still, that constitutes a user event, and not even one that changes the model. Those events presumably come in on the order of tens of milliseconds, so I wouldn't expect this to be a garbage collection problem?