emacs-request VS kele.el

That is quite normal thing to do. Have you not seen Emacs Async? Take, a look, it is a useful thing. Or Emacs Request. Since Emacs does not have proper thread scheduler, that is the best next thing you can do.

Exciting! I've been using request.el for my own projects mostly out of habit. Could you outline some of the relative advantages of plz?

Instead of shelling out to curl, use url.el or request.el.

You mean, John Wigley's async package? Maybe it isn't used so often, however async processes are used in Emacs. Check for example functions 'native-async-compile' or 'async-byte-compile-file'. There is another package, request.el that uses async processes to do the network I/O (via curl).

This? https://github.com/tkf/emacs-request

You can already use emacs-request, it offers very nice asynchronous API and uses curl by default if present and falls back on Emacs url if curl is not found.

Have you tried (package! emacs-request), since that’s the name of the source repository (https://github.com/tkf/emacs-request)?

It's possible that I'm brain dead but I'm struggling to wrap my head around the emacs-request code found here: https://github.com/tkf/emacs-request

I'm happy to announce the release of Kele 0.4.0, the "spritzy" Kubernetes cluster management package for Emacs. Changelog is available here.

I'm happy to announce the release of Kele 0.2.0. Changelog is viewable here.

Hot off the presses, a demo screencast of context-switching, just for you. I've added this to the README and the documentation site too. More to come. Cheers.

Just used plz to outright replace a homespun function of mine based on request that turned out to be simpler to replace than debug. Initial experience is very nice. Thanks!