Go Concurrency vs Elixir Concurrency - Elixir Melbourne Meetup

"🚀 Dive into the world of concurrency about Go and Elixir with Julian's enlightening talk at the recent Elixir Meetup! 👨‍💻🔧✨ #ElixirMeetup #GoConcurrency #ElixirConcurrency #SoftwareDevelopment

[@fixpoint]

Great talk, thanks for sharing. I liked seeing the comparison between runtimes. While Go is similar in many ways, in my opinion, the ergonomics of doing concurrent programming is much more complicated in Go. Channels have very specific semantics that can be tricky. And while the mantra may be to use CSP, lots of code I find uses mutexes to share memory instead. I think Erlang / Elixir is so much nicer in this regard.

[@madlep]

👋 speaker here. Thanks for that 😁was a fun talk (even if you can only see my legs). Definitely agree that the semantics and usage are totally different. The low level implementation of the runtimes share so many similarities, but the languages built on top them have little in common. In general, I find that concurrent code in Go makes systems LESS resilient and more brittle, whereas in Erlang/Elixir it is the opposite. In Go concurrency is a tool mainly for performance and scaling, rather than a way to build reliable system.

[@fixpoint]

@@madlep That’s a great observation about ergonomics and fragility. It’s one that I’d agree with based on my experience. And while I know we aren’t talking about Rust, I feel the same about its async/await implementation. Rust’s tagline of fearless concurrency falls flat on its face because one can make so many mistakes inadvertently that the compiler can’t help with.

[@michaelangelovideos]

Excellent video and presentation, thank you!