plz.el VS emacs-request

plz can make the network code easier to write: https://github.com/alphapapa/plz.el

I've released version 0.2 of plz.el, my HTTP library for Emacs Lisp that uses curl as a backend. This version includes a new feature, a simple request queue system. It works like this:

url-retrieve is definitely a bit awkward. I started working on plz, which I use in Ement.el. Lars also has a branch with a macro that wraps url-retrieve with a nicer API; he hasn't merged it yet.

Request is a good library in many ways, but you may also find my new plz.el HTTP library interesting. It's at an early stage of development and could use more testing.

fyi, the first link in the README appears to be broken: https://github.com/alphapapa/plz.el/blob/master/httpbin.org

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