Live data from Hacker News

Erlang/OTP 29.0

erlang.org

31–40 of 64 posts

Re: Erlang/OTP 29.0

#31

Earlier quoted context omitted.

I'd say Rails is faster than Phoenix (as in development speed) only for the first day or so. After that you'll stumble upon impicit logic, method-missing and this kind of stuff, which will require more time to figure out how it works. Elixi/Phoenix is more exlicit in that regard, making long-term support (as in anything past first week) a breeze. No hidden state, no figuring out where ModuleName.method(params) is com…

but if you want explicit any not just use django?

Elixir and Phoenix is a better production platform than Django.. I’m not throwing shade on Django, many production systems use it happily. I’m saying that Phoenix/Elixir is better, partly because of the BEAM and OTP and partly because of the language and the framework. Real concurrency. Better performance. Far more robust in production. The language is pre-compiled, and while not statically typed, that alone provides one more safety layer. It’s functional, which avoids a lot of the ugly patterns in both Rails and Django. It has a built-in fast and reliable KV store. It has distribution between the nodes if you want it (e.g. for a distributed cache). It enables you to debug with a remote shell connected live to the running system. There’s a lot more than I can add here.

Re: Erlang/OTP 29.0

#32

Earlier quoted context omitted.

but if you want explicit any not just use django?

Elixir and Phoenix is a better production platform than Django.. I’m not throwing shade on Django, many production systems use it happily. I’m saying that Phoenix/Elixir is better, partly because of the BEAM and OTP and partly because of the language and the framework. Real concurrency. Better performance. Far more robust in production. The language is pre-compiled, and while not statically typed, that alone provides…

if you want true concurrency, why not use goroutines? It provides single binary deployment and static types?

Re: Erlang/OTP 29.0

#33

Earlier quoted context omitted.

but if you want explicit any not just use django?

Django is not very different than Rails and imo much less ergonomic. Many issues are still there like hidden state/setup needed to call something

django requires more boilerplate and is less magic than rails.

Re: Erlang/OTP 29.0

#34

Earlier quoted context omitted.

Elixir and Phoenix is a better production platform than Django.. I’m not throwing shade on Django, many production systems use it happily. I’m saying that Phoenix/Elixir is better, partly because of the BEAM and OTP and partly because of the language and the framework. Real concurrency. Better performance. Far more robust in production. The language is pre-compiled, and while not statically typed, that alone provides…

if you want true concurrency, why not use goroutines? It provides single binary deployment and static types?

I am a Go dev, too. I consider Go my main language. The BEAM has a very, very similar architecture to the M:N scheduler in Go. Goroutines are not dissimilar to BEAM processes. You can similarly run thousands of processes on the BEAM. But Go does not have a real Phoenix equivalent and there are reasons to use Elixir and BEAM, especially on the web side, including some of what I already mentioned above.

Re: Erlang/OTP 29.0

#35

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

Phoenix is mostly interesting because of OTP and channels (and LiveView I guess but it's not a choice I would make in 2026) so if you don't need what they bring...

Ecto is not bad as well.

Claude Code is very good at writing Elixir.

Surprise, you'll be more productive with what you know, LLM or not.

Re: Erlang/OTP 29.0

#36
post #26

Earlier quoted context omitted.

I used both Rails and Phoenix. ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO, but not everyone shares the same feeling. Despite having built in concurrency my team ended up building a version of Sidekiq because supervisors don't cover all use cases of job control. I prefer deploying with Capistrano than with Elixir builds. Another matter of taste. Structural pattern matching is the only feat…

> ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO, but not everyone shares the same feeling. Well, depends on what you do. Ecto is closely follows SQL logic and allows to translate weird sql queries into code directly. All queries are explicit, e.g. you either do preload(...) or can't access nested records at all, no chance of N+1 by design. Changesets are also different and are just functions…

It's fun watching other languages orms be 10 years behind in design.

Your example is a common anti pattern from PHP orms 15 years ago.

Re: Erlang/OTP 29.0

#37
post #30
post #21

Earlier quoted context omitted.

I’ve been writing Elixir apps full time since 2016. Clients are very, very happy never to see a crash. In fact, all the applications I have deployed in production in the past 10 years have 100% uptime. (Apart from hardware, OS and network faults outside my control) You might want to broaden your horizons.

hello, would you please recommend a good resource to get started with elixir ? thanks for your time !

This is a good place to start:

https://elixirisallyouneed.dev/resources

Re: Erlang/OTP 29.0

#39
Is anyone still using Erlang for green field projects?

I know there are plenty of Elixir enthusiasts here, I mean plain ol' Erlang.

If you are still using Erlang, why do you prefer it to Elixir?

Post reply on HN