[asveikau]

I remember text editing UIs struggling when the machine was otherwise overloaded.

Although that started happening much more when text editors started to be written in garbage collected languages more often, which I put in the current century.

I still get that today if I use an old machine and/or a fancy text editor.

[wbl]

Emacs has always been written in Lisp, and it's possible for badly written code to make it lock up. Not a new complaint on low RAM machines where the gc and paging interact badly. But you need very low RAM by today's standards.

[asveikau]

Carefully worded with "more often" because I knew emacs was an outlier. I was never an emacs person myself so I don't know it first hand, but in do know people used to call it a resource hog a long time ago.

[titzer]

Emacs is largely written in e-lisp. Does it have problems with lag? I don't think so.

I think what made (makes) those editors laggy is a heavyweight representation of text and a creating a lot of garbage when processing said text.

[adrianN]

I regularly experience typing lag in Slack on a modern Macbook Pro.

[zwaps]

Well at least this retro experience is back with Javascript laden apps, that feel like they pull ui elements from a 56k connection