Hacker News Reader

Right, CFFI is another can of worms. It is sometimes questionable whether the time saved by reusing C code isn't lost by debugging and integration issues. For example I ended up avoiding cl-async (a wrapper over a C library) due to these.

In my mind reimplementing in CL is better bet than pulling Docker.

View on HN

Well, I did write quite a bit of CL code for money, but it's hard to get paid for reimplementing every library that one may need in CL ;(

I have not meant it in such extreme way at all :(

Just this: if something interferes badly with a basic CL feature such as SLIME (cl-async does), toss it.

cl-async works pretty well with SLIME if you use its SLIME REPL integration feature that I contributed several years ago. https://github.com/orthecreedence/cl-async/blob/master/src/r...

It basically starts an event loop in a separate thread and then wraps all of the SLIME's evals so they're executed from within that event loop.

> I ended up avoiding cl-async

What do you use instead?

I reimplemented the parts I needed using threads+usockets. There's no fundamental reason it can't be built directly on OS async interfaces, even without threading, instead of C library.

Reply on news.ycombinator.com