Erlang and its ilk are dumb hipster languages that are terrible for performance and for building useful things in the modern era. We need to stamp these out before impressionable children doom their careers by using them instead of Java, C++, Python etc.

>he's still mad
KEK

HELLO JOE
https://www.youtube.com/watch?v=uKfKtXYLG78

Discord proves you wrong.

>>105903200
trooncord has been migrating away from elixir to rust because they need better performance

>>105903428
only the parts that require native speed, the beautiful thing about higher level solutions that have FFI support is that you can drop to lower level to implement the performance critical parts
you cannot do the same the other way around

> reinvent the distributed computer wheel this time with C++
Nup. I use C++ where it's needed but that's not for scalable, secure servers and webservers.

>>105902824 (OP)
Only Elixir is the hipster language. It's for ruby programmers who got filtered by Erlang.

>>105903638
BEAM NIFs are limited by preemptive scheduling. A Python FFI to C that runs for any reasonably high amount of time will complete much faster than a dirty NIF from Erlang/Elixir. I suppose you could do it over a Port call but at that point why not just do it in C to begin with?

>>105904677
> but at that point why not just do it in C to begin with?
can you name a single service that wasn't backed by multi billion dollar conglomerate that runs at the scale of discord that was written in C?

> I suppose you could do it over a Port call but at that point why not just do it in C to begin with?
because I'll ended up having to re-implement part of the BEAM vm runtime just for some street cred from which I gain nothing

I used gleam the other day and for a language that compiles to JS it sure does have dogshit JS support. As far as I can tell I have to port every JS function and type I want to use so in effect I'm having to write bindings to JS for every project I want to compile to JS because the language has no concept of what JS is until it compiles. What a fucking joke, even swift is better than this because you can just paste C code, list it as a dependency in your config and start calling C functions. Meme langs gonna meme I guess.

Akka (JVM) and Orleans (.NET) both implement the actor model like Erlang, have inherent fault tolerance like Erlang and also aren’t slow as molasses, unlike Erlang. There is zero reason to use BEAM when Akka and Orleans exist. They have all the upside of BEAM with none of the downsides.

>>105904677
post code

>>105905424
>write bindings to JS for every project
>he doesn't know what a library is

>>105906165
JVM and NET do not have the same scheduling mechanism as BEAM, which means they are dead on arrival
how fucking difficult is it to grasp that the uniqueness of BEAM is not its fucking message passing or whatever, but its soft realtime characteristics and no pause the world GC?
with BEAM I can spawn a process that runs for a year, doing some pure mathematical shit, and it will not hog CPU time, ever

>>105906246
Ok but in other languages I can just copy c code into my source files, start calling it and compile it like I would any other soruce file. Why can't I call js stdlib functions like this in a language that so called targets js as a compile target? Pathetic js support.

>>105906275
Not inherently but they do with Akka and Orleans.

>>105906524
no, they don't
post a fucking source or shut your bitch ass up

Go is only marginally less concurrency-capable than Erlang but it’s substantially faster for CPU bound stuff. Overall a much simpler way to reason about concurrency too.

>>105906967
>completely ignoring the concept of shared state
you do not know what you are talking about

>>105906976
Shared state isn’t a problem if you git gud

>>105906976
Lol what's wrong with shared state? Also there is nothing stopping you from making copies in <insert imperative language here>.

>>105907071
cniles can not write bug-free shared state

>>105907396
>Projecting my skill issues onto others

>>105907451
please share some examples then

>>105903717
Erlang does not have macros or lazy stream protocol
you are unironically a pleb that thinks he is cool for choosing the base technology, like a person that wants to drive a manual rather than an automatic

>>105907705
All the best drivers in the world drive manuals though.

>>105907396
We aren’t talking about C, we’re talking about Go.

>useful things in the modern era
Proceed to disqualify a runtime with concurrency and distribution built in because it doesn’t crunch numbers fast enough. Erlang is perfect for programming server side code, if raw floating point speed mattered so much node wouldn’t exist.

>>105907897
Node is even worse and an atrocity unto software development that exists solely to let people who shouldn’t be programmers make horrifically shit webapps. Using it as a hurdle to clear is pathetic.

>>105902824 (OP)
>Continued
prev >>105885207

Erlang walked so Go could go run()