@newt
Getting paid for fixing someone's Blenomber? Sounds like shitposting gone horribly wrong! 🫠
@newt
Man, it was an obvious joke, you didn't have to go into the trouble of explaining that you aren't going to fix other people's Blemora for moneh 😄
@newt
Oh, I see, it was a tiny bit of wishful thinking 😁
I've never really used Erlang, but I did like it… like 14 years ago — but now we have decent massive parallelism in nearly every language, so I'd probably go with Go instead. I would use Go for a lot of things, but having Google at the helm ruins it for me — very disappointing 😩
Though, the way BEAM manages heaps is interesting. Erlang threads each has its own heap, so a thread can be stopped, GC'd, or even moved to another machine altogether without any disruption. The lack of any internal state in threads outside of the current execution stack also helps here.
@newt
> massive parallelism isn't the distinctive feature of Erlang
Well, it used to be — green threads (and in case with Erlang, green processes) weren't a built-in feature in many languages at the time, and being implemented externally made the code feel clunky.
Nowadays Go comes with both coroutines as a built-in language feature and channels as an efficient form of IPC, in Rust they are still external to the language, but with syntax extension do not feel so clunky.
