News for hackers. Stuff that matters.
Re:Bringing GNU Emacs to Native Code (2020) by geokon on Sunday May 02, 2021 @03:48AM (#27013153)
last I tried VSCode there was a noticeable input lag (keystroke to character on screen). Is there some trick to fix this?

I found it incredibly distracting. In Emacs... Magit is instantaneous while orgmode tangle/export is embarrassingly slow - but never a dealbreaker

anecdotally eshell has some of the lowest latencies as well https://danluu.com/term-latency/

Re:Bringing GNU Emacs to Native Code (2020) by andai on Sunday May 02, 2021 @04:54AM (#27013477)
I switched back from VSCode to Sublime Text (despite enjoying Intellisense) due to how much more responsive the scrolling is in Sublime.
Re:Bringing GNU Emacs to Native Code (2020) by nxpnsv on Sunday May 02, 2021 @05:08AM (#27013572)
Same here, maybe it’s only in my head, but for me subl is just better.
Re:Bringing GNU Emacs to Native Code (2020) by darthrupert on Sunday May 02, 2021 @08:12AM (#27014586)
It is massively better in latency than any other editor I've tried. No surprise, since I believe it's C++.

Unfortunately sublime's plugin ecosystem isn't very lively.

Re:Bringing GNU Emacs to Native Code (2020) by agumonkey on Sunday May 02, 2021 @07:08AM (#27014115)
I couldn't even type 2 chars in vscode on a 2nd gen i5. To be fair it's been decades since I've experienced that amount of delay. Thanks I guess
Re:Bringing GNU Emacs to Native Code (2020) by stjohnswarts on Sunday May 02, 2021 @12:37PM (#27016572)
If you're have a problem with performance in vscode 95/100 times it's memory not cpu bound. Obviously emacs uses less memory than vscode, at least at base configuration.
Re:Bringing GNU Emacs to Native Code (2020) by agumonkey on Sunday May 02, 2021 @01:09PM (#27016872)
Maybe, it's still incredible to think that memory pressure would create that much latency. And I'm not that picky, I use a hp48 calc (on which lag is almost a feature). I'm just shocked when people say emacs is sluggish while vscode flies.