3 ms·

I've never understood this criticism. Elisp is single threaded. Emacs has long had async capabilities with process buffers and sentinel functions.

• philsnow 5y ago
  UX depends heavily on the quality of the packages in your init.el; if a maintainer has gigabit fiber at home and writes their elisp to hit the network during `(interactive)` elisp, it's going to feel slow for people on worse connections. emacs/elisp aren't all that opinionated, there's lots of rope to shoot yourself in the foot with
  • taeric 5y ago
    My concern is that this will remain the case, even when Elisp goes multi threaded. Such that most concerns won't really change, at all.
• hestefisk 5y ago
  Got it, thanks for clarifying. It was not a criticism, merely curiosity. :) I used to use Emacs back in the late 90es; since then I have mainly used vi in various permutations.
  • taeric 5y ago
    Apologies if my post came off as harshe. I see this critique a lot, but it doesn't make sense to me. Especially since compilation mode has existed forever. I do grant that some things could use extra support for async, so it will be a welcome addition. But there is already a lot of capability today.