haha, I definitely wouldn't call my setup fast. But it did get a lot better after Native Compilation and a lot of the major stuff has started async to feel more responsive at least.
reply> It's fast.
replysuper slow on windows
That's surprising considering it was fast on computers from 30 years ago
replySame on macOS. Could be that we are missing some native compilation option though
replyIt’s slow, bloated and packed to the brim with “features” you will never need.
replyThere is Only One. En garde!
>You won't suddenly find your text editor "upgraded" with tons of new features you never asked for.
replyI never asked for native compilation implemented via the trampoline technique, which increases attack surface (because it causes Emacs to routinely execute files in a known-by-attackers location in my home directory) and makes debugging harder, but I'm stuck with it if I want my Emacs to speak the Wayland protocol (and I do).
Ditto the clumsy bolting-on of lexical scope.
Native compilation is optional as you surely know.
replyIt also has nothing to do with Wayland.
And what's wrong with adding lexical scope!?
I do have some concerns about certain features but the ones listed do work, and work great.
You can't build an Emacs with Wayland (PGTK) support without native comp. ./configure will complain and refuse to do it.
replyThis sounds like a bug! I mean, this makes libgccjit a hard dependency for pgtk which just doesnt make sense
replySigh. Don’t be “that guy.”
reply[dead]
reply