Hacker News Reader

Comment by colesantiago | Hacker News Reader

I see Elixir on here quite often, what is the appeal and why are many companies switching to Elixir?

Last I checked a while ago Brex famously used to be on Elixir but now are on Kotlin.

https://medium.com/brexeng/building-backend-services-with-ko...

Elixir+Phoenix does web stuff very well, with little maintenance required (i've upgraded 4+ years old project in two ot three days, time mostly spent on upgrading some 3rd party libs that bumped major version). Unlike ruby, it's really easy to understand what's going on (no hidden state, all variables are passed explicitly, imports are stored in one file (in phoenix) you can look at or explicit as well.

With added LiveView on top, you could avoid writing a lot of SPA react (vue, svelte etc) code (some limitations apply, but you can do a lot), spending less people, time and resources for the same result.

Traditional setup: backend logic + backend api + react SPA + logic for calling backend api

LiveVew setup: phoenix backend + LiveView views + a bit of glue code (in elixir) to replace onclick etc stuff

For those reading who are not able to switch stacks, these same ideas are being applied in other languages very successfully as well.

1. Laravel Livewire for PHP

2. Hotwire for Rails/Ruby

3. Blazor for C#/.NET

4. HTMX* as a general tool for any other web server

5. React Server Components (if you squint hard enough)

Phoenix Liveview definitely started the trend by showing a mature implementation of these ideas on the same level as the application developer.

I would argue number 5 is a bit of a meme, since you still have to write a ton of JS, but if you're more interested in the architecture ideas for structuring your app, there is an interesting parallel that I think can be drawn.

[*] HTMX doesn't really embrace the idea of calling a function from your server by name, but the ergonomics are similar when writing frontend code.

Laravel Livewire is… frustrating. I used it for 1-2 years and ended up learning Elixir so I could use LiveView instead.

Livewires performance is terrible for anything other than very basic components. The fact that it has to rebuild state on every interaction makes it a pretty poor tool for most use cases.

Not sure if you've seen that v3 was released. Caleb spent a lot of effort to solve many of the performance problems. It's still not as lean as Liveview (and nothing probably will be) but it's much much better than it was.

I saw it was released but never looked into it as there's no reason to now that I've moved to LiveView.

I have other issues with Livewire as well, including how Caleb operates his communities. He has and continues to make a ton of money off Livewire and still provides zero support to the community. Want any actual support? Well that starts at $6,000/year for one support request a month.

He doesn't even appear to be a member of his own discord server anymore. Not that it makes a difference; last time I checked had only ever sent 34 messages in there and the last one was in 20202. He has one guy who would randomly show up around once a day and answer some of the questions.

I don't expect free support but if your package is so confusing that the community is unable to support each other, you should probably be around trying to help sort that out. Instead, he just keeps doing re-writes which puts the the load on everyone else.

Anyways; if you're interested in this type of project I HIGHLY recommend you check out Elixir/Phoenix/LiveView. I haven't enjoyed writing software this much for a long time; not only is the language and framework more enjoyable to work with, but the community is so much better in general.

I can't speak for other companies or devs, but as a relatively junior developer I quite enjoy working in Elixir, and especially with Phoenix and the Ecto ORM.

The syntax reads and writes very well. When I now have to write other languages, mainly Typescript, I miss native pattern matching and the pipe operator.

Plenty of languages can get a solid standard library to write most code with, but only elixir gives you a modern, simple standard library with the tools to scale an app as high as apps can be scaled.

Whatsapp famously got to 1 billion messages a day with only 11 engineers on the BEAM (the VM that elixir runs on). It has proven itself immensely capable at the highest levels of scale so the only thing for anyone to decide is whether the stdlib and tooling is to their liking (speaking mostly in the context of networked IO bound applications, which is most things on the internet)

I love Elixir, but I don't agree that it's the only language with a great standard library. Go has one too.

I probably worded my statement poorly, but my intention wasn't to claim it was the only language with a great stdlib. I would disagree that go has a good stdlib, I think it's quite poor, but I do believe plenty of other languages have great stdlibs.

We (Mirego) made the move from Rails to Elixir years ago for three main reasons: productivity, maintainability and performance → https://shift.mirego.com/en/elixir-functional-programming

Really interesting read! I was always curious about Elixir but we've been using kotlin in the backend for years now an I'm really happy (except the JVM and spring bullshit stuff). The language tho is on another level. Lot's of compile-time safety and syntatic sugar. We're really productive with that.

My understanding from talking to some former Brex developers was that the switch was entirely because Kotlin is the CTO's favorite language and everything else was just a post-facto justification. So take it with a grain of salt.

"many" not really.

Elixir is bolted on top of erlang so reading error stacks with erlang is common, needing to grok erlang concepts and docs is also sometimes needed. This makes it odd to work with. I know if I'm using a Java, Ruby, Python or PHP framework (django, laravel, rails, whatever latest java web framework) I can read thru docs or source code and troubleshoot stack traces without having to learn another language. Its unavoidable with Elixir beyond simple apps.

I barely know Erlang and life has been fine. I do know the runtime characteristics of the Beam VM and occasionally I need to read Erlang docs, but compared to other stacks the experience has been significantly more pleasing.

People are of course different and I fully acknowledge that things that seem normal to me may seem odd to others, so YMMV.

Erlang is a very simple language though especially compared to elixir. The runtime semantics are fairly unusual but it almost completely shares those with elixir so you'll have to learn them anyway. The BEAM is very complex but again you have to learn that anyway.

I hear you and it has been an issue years ago but gradually Erlang's maintainers have been making error messages (and return error values) better and more readable and at this point I can't remember when was the last time when an Erlang return value and stack trace have impeded me.

So you were correct some years ago but I am not seeing this nowadays. So yeah, valid criticism, at the same time this criticism has been mostly taken to heart and addressed as of today.

The syntax is a little different but the semantics are exactly the same, so it's trivial I guess?

also, the errors you get, when they are in erlang are in valid erlang, i can't say that about Java, Ruby, Python or PHP which give you errors in English.

https://hackernoon.com/why-is-erlang-the-only-true-computer-...

For some things like SSL/TLS, Elixir is mostly just syntactic sugar over erlang features. I didn't find it trivial when I was trying to figure out SSL/TLS issue but worked fine on same OS but different language stack. Keeping track of versions+patches of Erlang, Elixir and Phoenix for a web app may be trivial until you run into something where its not Elixir then you have to dive into erlang things. I was merely pointing out it is in fact another step people may have to take. Something to consider when evaluating languages. I ran into this with an app that does a lot of API calls externally, dealing with many varying TLS certificates.

Fans of Elixir out in force today downvoting dissenting opinions even though its valid.

All opinions are valid. this point isn't particularly special though.

In almost every lang you'll run into something that your aren't familiar with and you'll have to dive into something you aren't comfortable with. I had to dive into some C code when ruby decided to segfault. I've had to dive into Java JVM internals when working in Clojure.

So I'm not sure this is a "elixir" thing as much as a "I'm a developer thats supposed to know multiple languages and stacks" kinda thing.

Reply on news.ycombinator.com