← Back to context

Comment by mfkp

6 days ago

What's wrong with ruby in this case? Ruby in 2024 can easily handle an app like this.

Let's flip the question. What is it that Ruby does better than Elixir for this domain?

I can't think of anything. One could argue that Ruby might have a larger package repo to pull in dependencies from, but this being a telecom adjacent domain you'll find that Elixir and OTP solves some tricky problems rather well that mainly object oriented languages tend to struggle with.

You'd also get out of having to skip between your application language and Golang down in Livekit, since the Membrane folks have built a standalone WebRTC platform: https://github.com/elixir-webrtc

In production Ruby code bases also tends to degrade over time. The team will sometimes find itself under duress and push magic tricks that Ruby allows to prod. Perhaps it's a matter of taste or whatever, but I've found most of the Rails applications I've come across somewhat hard to learn and debug. Similar to annotation driven applications in Java things can get really weird and brittle. These things are harder to accomplish in Elixir, which also seems to get a rather clever gradual typing system.