Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Just look at the readme. It says 100 FPS. Vim isn't even close to that, and Vim sucks with large files.


The only benchmark I could find is https://pavelfatin.com/typing-with-pleasure/#editor-benchmar... , showing GVim to be quite a bit better than that. For terminal Vim, terminal latency dominates.


That page doesn't list FPS at all.


What do you think FPS means in the context of a terminal text editor? The linked page is pretty clear in what the author means: “Cursor movement and edits render under 10ms”. So FPS = 1 / latency. The link I gave measures latency; < 10ms is > 100 FPS.

(Though I doubt the statement re: Zee < 10ms latency in practical terms. I think only xterm and Terminal.app are consistently below that in terms of pure terminal latency)


I said FPS, I didn't say latency. Please stop trying to argue against a point I'm not even making.


Fortunately, I don't type 100 characters per second.


Noob




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: