3 ms·
I'm conceptually a fan, but then I noticed its effect on my actual CPU fan. Whatever this is doing for rendering the Markdown is not cheap -- a single keystroke
by kemayo 12y ago
I'm conceptually a fan, but then I noticed its effect on my actual CPU fan. Whatever this is doing for rendering the Markdown is not cheap -- a single keystroke in the editor pane on the sample document triggers 5+ seconds of max-CPU usage.
Typing causing loud fan noises from my laptop is not the most restful experience.
https://www.dropbox.com/s/qy6szsbjs7cw3uv/Screenshot%202014-06-25%2020.17.17.png https://www.dropbox.com/s/qy6szsbjs7cw3uv/Screenshot%202014-...
- adamnemecek 12y agoI've had the same experience with like all Markdown editors that have a preview function. It does indeed suck.
- copperx 12y agoThat's shameful. It's not like they're running LaTeX behind the scenes. I think it boils down to the implementation of the Markdown engine.
- m_eiman 12y agoI've been using Erato and haven't had that problem. Might be worth a try... https://itunes.apple.com/se/app/erato/id658913051 https://itunes.apple.com/se/app/erato/id658913051