2 ms·

I’ve used libaco with a lot of success in the past (mixing uv, curl, and zlib in a way that made the zlib loop easier to manage (since it looked like a normal r

I’ve used libaco with a lot of success in the past (mixing uv, curl, and zlib in a way that made the zlib loop easier to manage (since it looked like a normal read, decompress loop with all context stack local). Any notes about why I would try Neco in the future?

dkjaudyeqooe 3y ago
This has support for ARM processors. It's nice to have multiple options. For instance the interface can be very different.