> Multithreading just sidesteps the problem while introducing its own can of worms.
In the meantime we're all stuck waiting for package downloads. I don't know the specifics about why emacs can't move to a concurrent model but it's embarrassing at this point
> The current async facilities are fine by me (I don’t use any auto* things, so YMMV).
Yes, it is clear the people who maintain emacs are fine with it. This is why using emacs in 2026 is so shitty.
How long does it take to start emacs for you?
> Multithreading just sidesteps the problem while introducing its own can of worms.
In the meantime we're all stuck waiting for package downloads. I don't know the specifics about why emacs can't move to a concurrent model but it's embarrassing at this point
> The current async facilities are fine by me (I don’t use any auto* things, so YMMV).
Yes, it is clear the people who maintain emacs are fine with it. This is why using emacs in 2026 is so shitty.