Why We Chose Erlang over Java, Scala, Go, C

waste of time watching this...

Project Manager to devs: hmmm....i want an omlette this morning
Devs: Sounds like a job for MICRO SERVICES !!
Project Manager: Hmm...i really want some bacon.
Devs: I gotchu bro ! Imma make a micro service for that.
.....everyone thinks micro-services is just this silver bullet to everything....ugh

Never answered the question. "Why we choose Erlnag"

The guy murdered the language. I wonder if they are still in business.

MongoDB is webscale ..

Boring talk even for washing dishes... 17 minutes in and it hasn't started yet.

OOP is bad programming practice. Writing spaghetti code hanging around is better for job safety.

Coz you guys want to enter niche market and save your jobs from being replaced. There are fewer Erlang developers compared to Java developers.

very inspiring to focus the whole thing from the approax of business cases an actual need and speaking about the initial monolith previous choices

I really missed the arguments against other languages. I am a programmer and Elixir enthusiast but even though I couldn’t find the selling points for Erlang in this case.
Lack of reasons and lots of personal points. Unfortunately it was a wast of time based on title but still some good points about Erlang ecosystem
Not fair in the end

Scala is better than Java, Go, C and Erlang/Elixir as a programming language because it has rich type system.

Is anyone else annoyed that the presenter keeps using the word "uhm"

Worst presentation I've seen in a long time. And such shallow, biased and incomplete arguments.

Drinking koolaid, much? Title could have been: "Here are some vague claims we used to convince ourselves to use Erlang" or "We are a startup, so we chose Erlang because on Hackernews..."

1. JVM, Erlang, Go and Node all have a stop the world GC, so what is your point?
2. The JVM has the best runtime visibility tooling of the bunch and should be the fastest for your workloads, where are the benchmark numbers?
3. Go doesn't outperform Java, its GC pauses shorter on average, yes. Shenandoah GC for the JVM also manages <1ms pauses on 100GB heaps, if you want low latency. But for your workload you'll want max throughput, in fact a few longer stop the world pauses result in a shorter runtime overall compared to many small stops.

IMO Scala with Akka would have been the best choice here if you fancy functional programming, actors, performance, runtime visibility and hiring, but luckily as a startup your first concern is making money.
If the title were: "We ported our Node app to Erlang, this is what we like about it and what we've learned", it would have been a fine case-study.

As a reminder - Facebook dropped Erlang and replaced it with CPP.