News for hackers. Stuff that matters.
Re:Common Lisp vs Racket by pdimitar on Tuesday September 06, 2022 @07:06AM (#32735427)
Honestly, there are way too many programming languages already. Even though a chunk of them are interesting as thought experiments and potential future investments (like that one that content-addresses its own AST; forgot the name), I believe it's high time we all focus on more practical aspects.

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.

Re:Common Lisp vs Racket by medo-bear on Wednesday September 07, 2022 @06:23AM (#32748782)
> I'd kill for a LISP with strong(er) static typing

interestingly, the person you are replying to is an author of this little lib

https://coalton-lang.github.io/

Re:Common Lisp vs Racket by pdimitar on Wednesday September 07, 2022 @08:05AM (#32749503)
Heh, quite nice. I wish LISP in general standardized something like this.
Re:Common Lisp vs Racket by medo-bear on Wednesday September 07, 2022 @09:16AM (#32750142)
its not necessary to standardize it. there are enough primitives in the standard. instead the language can be extended through libraries such as this