All of that barely matters to me. Where's the transparent parallelization? 2022 is going to be over soon, no language has any excuse to lack an easy way to do message passing and automatic thread pool management like Erlang and Rust's `tokio` do.
Not having a corporation back the development of a language has tons of downstream effects, including:
- lack of support opportunities
- lack of employment opportunities
- lack of evolution and development of an ecosystem
- higher churn and/or attrition
- fewer opportunity to do long-term design and implementation projects
Yes, sometimes there are FOSS miracle workers who are so extraordinarily productive without being paid, but they're few and far between.
(Aside from that, not all users need such functionality.)
Parallelism is one of those. Only microcontrollers are single-core these days, and not even all of them.
I sympathize with the people who have fallen in love with their own idea and are sad that others "don't see the light" and don't support them -- but our world is an imperfect system and that's a fact of life.
F.ex. I'd kill for a LISP with strong(er) static typing plus Erlang's transparent parallelism and runtime but yeah, we don't have that. So Elixir and Rust it is for me.
interestingly, the person you are replying to is an author of this little lib
Racket /also/ has `thread` which is a co-routine but afaik you cannot pass the co-routine off to another native thread and there are certain constraints passing data between different threads, similar to transferring ownership.
I am not aware of the SBCL ecosystem to comment.