#Erlang is neat. So is #LFE (#LispFlavouredErlang) and #Elixir (but less because #Lisp).
Once, there was also a way to interface #CommonLisp with Erlang using #CLERIC or the #CommonLispErlangInterface. At the moment though, I'm not sure if that's still compatible with the current state of Erlang.
I'd need to test.
Follow
@lispi314 what do you like about Erlang? Beyond the simplicity, the pre-emptive VM is important, I feel, to keep systems responsive. Backends, yes, but also a desktop written in Erlang would have a better chance of not locking up if it managed the video card leveraging the OTP. Not a heavy idea, especially compared to TailsOS etc.
@tetrislife Among other things, the shared-nothing approach to state & pervasive message-passing makes a number of bugs simply not a problem in Erlang.
The automatic scaling that its scheduler provides by fully exploiting available CPU cores without having to modify the program is also pretty nice.
Said scheduling & job management being able to then scale onto a cluster setup is also really neat.