terminal_prognosis

but the point is the language is the only layer boundary. Once you're in Elisp there is no boundary, no layers. You may choose not to go there, but the only thing stopping you is your own choice.

You'll need to explain that to those of us who use Emacs for professional work. What fails for you? In particular, what fails that needs threading to be resolved?

Yep - there's a reason asyncio event loop programming is popular in Python/JS/Rust etc.. People act like it's a crusty old inferior technique to the delights of multi-threading. In reality it often keeps things much simpler, is very powerful, and only leads to blocking behavior when it's badly coded.

Networking activity is a prime example of something where threading is least likely to be a clearly superior solution. Heavy CPU use is where threading may be the superior choice and a single event-loop thread is not. IO waiting is not.

Are you sure the problem there is threading? I'm pretty sure it is not. There's very little CPU usage. The problem is TRAMP is written synchronously when it should be asynchronous, not that it doesn't have threads.