logoalt Hacker News

SBCL Fibers – Lightweight Cooperative Threads

146 pointsby anonzzzieslast Saturday at 11:22 PM34 commentsview on HN

Comments

mark_l_watsonlast Sunday at 1:18 PM

I am excited by the proposal and early work. SBCL Common Lisp is my second most used programming language - glad to see useful extensions. Most of my recent experiments with SBCL involve tooling to be called by LLMs/agents and high speed tooling to provide LLMs/agents with better long term memory and context. Fibers will be useful for most of that work.

show 1 reply
smallstepformanlast Sunday at 5:56 AM

256Kb stack per Fiber is still insane overhead compared to Actors. I guess if we survey programming community, I’d guesstimate that less than 2% of devs even know what the Actor model is, and an even smaller percentage have actually used it in production.

Any program that has at least one concurrent task that runs on a thread (naturally they’ll be more than one) is a perfect reason to switch to Actor programming model.

Even a simple print() function can see performance boost from running on a 2nd core. There is a lot of backround work to print text (parsing font metrics, indexing screen buffers, preparing scene graphs etc) and its really inefficient to block your main application while doing all this work while background cores sit idle. Yet most programmers dont know about this performance boost. Sad state of our education and the industry.

show 5 replies
nothrabannosirlast Sunday at 4:59 AM

I strongly recommend having a look at the mailing list to get some context:

https://sourceforge.net/p/sbcl/mailman/sbcl-devel/thread/CAF...

and

https://sourceforge.net/p/sbcl/mailman/sbcl-devel/thread/CAC...

This will certainly speak to some people taking part in some of the more controversial discussions taking place on HN recently, to put it mildly.

show 2 replies
HexDecOctBinlast Sunday at 2:59 AM

Is there a similar document for the memory arena feature? I tried searching the official documentation, but found scant references and no instructions on how and when to use it.

show 1 reply
nesarkvechneplast Sunday at 8:28 PM

Every move in the concurrency direction is good but I really wanted to see preemptive scheduling and Erlang-like processes.

matthewfcarlsonlast Sunday at 12:43 AM

I personally like the name fiber better than green threads. But everywhere I’ve worked in user space cooperative threads, it’s always been green threads.

show 1 reply
theParadox42last Sunday at 6:21 AM

I really thought this was gonna be a sick material science paper. Still cool though

lukasblast Sunday at 5:39 AM

Serious question - I thought LLMs were bad at balancing parentheses?

show 2 replies
pestatijelast Sunday at 4:18 AM

SBCL - Steel Bank Common Lisp

justinhjlast Sunday at 12:33 AM

They should be called Anthony Green Threads. Seriously though, great to see.

stainluyesterday at 2:22 AM

[flagged]