emacs-request VS oneTBB

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

Use a library like https://github.com/oneapi-src/oneTBB

tbb

I have a project that depends on Intel's oneTBB. My project is structured as follows:

Intel TBB is still being maintained, it's just renamed to "OneAPI". The TBB part can be found here: https://github.com/oneapi-src/oneTBB

$ cd /tmp $ wget https://github.com/oneapi-src/oneTBB/releases/download/v2021.7.0/oneapi-tbb-2021.7.0-lin.tgz

For a more fully featured version of that idea with parallel algorithms and data structures, there are libraries like Thread Building Blocks.

Users should work with higher level primitives like tasks, parallel loops, asynchronous functions etc. Think TBB, Thrust, Taskflow, lparallel for CL, etc.

Consider using oneAPI Threading Building Blocks instead of naked threads.