Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Erlang/OTP 29.0

erlang.org

Post reply on HN
Print view View original

11–20 of 64 posts

Re: Erlang/OTP 29.0

#11

Post by dnautics »

hackernudes wrote: post #9
tmoertel wrote: post #6

For anyone wondering what the "OTP" part is in Erlang/OTP, it is a set of libraries and associated principles that, in effect, standardize the creation of highly reliable, fault-tolerant applications, originally for the telecom domain. It's worth checking out the brief introduction to the fundamental ideas in the introduction to "OTP Design Principles": https://www.erlang.org/doc/system/design_principles.html

OTP = Open Telecom Platform

no longer. That is legacy. OTP now just stands for "OTP"

Re: Erlang/OTP 29.0

#12

Post by dnautics »

sbrother wrote: post #10
ch4s3 wrote: post #7

I'm interested to see how records play out in the ecosystem.

I was about to say "what, we've had records for decades" but then I read the changelog. Interesting. I wonder if there a world where Elixir starts compiling maps to "native records"?

probably not maps, but structs yes.

Re: Erlang/OTP 29.0

#14

Post by faangguyindia »

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.

I don't write directly in Go because, it consumes lot more token when the app scope is unknown but it's very efficient for rails.

These day i don't need react or angular anymore, i use Hotwire in Rails and HTMX in Go.

Erlang forum itself uses Discourse (written in Rails)

Re: Erlang/OTP 29.0

#15

Post by davidw »

hackernudes wrote: post #9
tmoertel wrote: post #6

For anyone wondering what the "OTP" part is in Erlang/OTP, it is a set of libraries and associated principles that, in effect, standardize the creation of highly reliable, fault-tolerant applications, originally for the telecom domain. It's worth checking out the brief introduction to the fundamental ideas in the introduction to "OTP Design Principles": https://www.erlang.org/doc/system/design_principles.html

OTP = Open Telecom Platform

"Outlaw Techno Psychobitch"

https://www.youtube.com/watch?v=rRbY3TMUcgQ

Re: Erlang/OTP 29.0

#16

Post by ramchip »

dnautics wrote: post #11
hackernudes wrote: post #9

Earlier quoted context omitted.

OTP = Open Telecom Platform

no longer. That is legacy. OTP now just stands for "OTP"

It's still referred as such through the official documentation: https://www.erlang.org/faq/introduction.html#idm24

You may be thinking of comments like: https://erlangforums.com/t/should-otp-be-the-standard-librar...

Re: Erlang/OTP 29.0

#17

Post by tommica »

faangguyindia wrote: post #14

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.…

Erlang != Elixir - but otherwise a good question. I think WhatsApp uses erlang

Re: Erlang/OTP 29.0

#19

Post by toast0 »

ksec wrote: post #13

Does anyone knows if WhatsApp is still based on Erlang?

I don't have first hand knowledge (I left in 2019), but WhatsApp's public Erlang related repos are still active, and afaik, Erlang didn't escape into Meta at large, so if WA had moved off, there's no sense working on Erlang after that.

Re: Erlang/OTP 29.0

#20

Post by sph »

You might want to update prod apps ASAP to this or the latest point version if below 29. Just deployed an app to production, automated security scans found 2 CRITICAL CVEs and half a dozen of HIGH risk ones dated Feb-May 2026.
Post reply on HN