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

Erlang/OTP 25.0 Release

erlang.org

Post reply on HN
Print view View original

21–30 of 125 posts

Re: Erlang/OTP 25.0 Release

#21

Post by brightball »

jacquesm wrote: post #7

Have there been benchmarks of the JIT vs say JS or the JVM?

BEAM is never going to win for straight line speed. This is going to be an improvement for a language optimized for resilience, concurrency and consistency.

Running millions of concurrent processes, with their own heap, with consistent response times that individually tolerate failure without negatively affecting the entire system is just a different animal with a different set of trade offs.

You’re trading some speed for those benefits.

Re: Erlang/OTP 25.0 Release

#22

Post by davydog187 »

Jeff_Brown wrote: post #20

I taught myself Erlang last year and loved it until I tried to write an application. The OTP documentation, while voluminous, was confusing and seemed to have important omissions, and I found little if any community.

There is a huge community, not just in Erlang, but in the larger BEAM ecosystem. Have you tried the Erlanger or Elixir slack? We also have https://erlangforums.com/ and https://elixirforum.com/. For smaller BEAM languages like Gleam, we have Discord available https://discord.com/invite/Fm8Pwmy

There's a lot of great stuff in the BEAM ecosystem, I would caution on writing it off too fast

Re: Erlang/OTP 25.0 Release

#24

Post by Jeff_Brown »

davydog187 wrote: post #22
Jeff_Brown wrote: post #20

I taught myself Erlang last year and loved it until I tried to write an application. The OTP documentation, while voluminous, was confusing and seemed to have important omissions, and I found little if any community.

There is a huge community, not just in Erlang, but in the larger BEAM ecosystem. Have you tried the Erlanger or Elixir slack? We also have https://erlangforums.com/ and https://elixirforum.com/ . For smaller BEAM languages like Gleam, we have Discord available https://discord.com/invite/Fm8Pwmy There's a lot of great stuff in the BEAM ecosystem, I would caution on writing it off too fast

I know there's a lot of power there. Whatsapp was written in OTP and had something like half the world using it with a development team of maybe 12.

I'm glad to hear the community is bigger than what I found. I don't actually remember that search process. What I remember clearest was running into the brick wall of the OTP documentation.

Re: Erlang/OTP 25.0 Release

#25

Post by davydog187 »

Jeff_Brown wrote: post #24
davydog187 wrote: post #22

Earlier quoted context omitted.

There is a huge community, not just in Erlang, but in the larger BEAM ecosystem. Have you tried the Erlanger or Elixir slack? We also have https://erlangforums.com/ and https://elixirforum.com/ . For smaller BEAM languages like Gleam, we have Discord available https://discord.com/invite/Fm8Pwmy There's a lot of great stuff in the BEAM ecosystem, I would caution on writing it off too fast

I know there's a lot of power there. Whatsapp was written in OTP and had something like half the world using it with a development team of maybe 12. I'm glad to hear the community is bigger than what I found. I don't actually remember that search process. What I remember clearest was running into the brick wall of the OTP documentation.

I'm not sure on your exact timeline, but the documentation has also seen several upgrades.

For example, see the "telemetry" library, written in Erlang and published to the Hex repository. Its documentation is built using the Elixir-based ex_doc https://hexdocs.pm/telemetry/readme.html

Re: Erlang/OTP 25.0 Release

#26

Post by haolez »

I've seen more than once recently an engineer saying that software solutions outside of the Serverless ecosystem (FaaS, DB, etc) is "the new legacy". And that cloud providers have solved all the pains that Erlang was supposed to address.

What's your feeling on this? Elixir sounds very compelling to me, but I worry that I might be going in a direction that's not where the industry is going.

Re: Erlang/OTP 25.0 Release

#27

Post by rz2k »

igouy wrote: post #23
jacquesm wrote: post #7

Have there been benchmarks of the JIT vs say JS or the JVM?

fwiw https://benchmarksgame-team.pages.debian.net/benchmarksgame/... fyi "1.4 What sort of problems is Erlang not particularly suitable for?" https://www.erlang.org/faq/introduction.html#idp32114576

With Nx[1], there might be fewer limitations than there used to be.

https://news.ycombinator.com/item?id=26168304

Re: Erlang/OTP 25.0 Release

#28

Post by haolez »

I've seen more than once recently an engineer saying that software solutions outside of the Serverless ecosystem (FaaS, DB, etc) is "the new legacy". And that cloud providers have solved all the pains that Erlang was supposed to address. What's your feeling on this? Elixir sounds very compelling to me, but I worry that I might be going in a direction that's not where the industry is going.

Re: Erlang/OTP 25.0 Release

#29

Post by davydog187 »

haolez wrote: post #28

I've seen more than once recently an engineer saying that software solutions outside of the Serverless ecosystem (FaaS, DB, etc) is "the new legacy". And that cloud providers have solved all the pains that Erlang was supposed to address. What's your feeling on this? Elixir sounds very compelling to me, but I worry that I might be going in a direction that's not where the industry is going.

Serverless? You mean vendor lock-in, distribution issues and reproducibility issues, etc?

Re: Erlang/OTP 25.0 Release

#30

Post by haolez »

davydog187 wrote: post #29
haolez wrote: post #28

I've seen more than once recently an engineer saying that software solutions outside of the Serverless ecosystem (FaaS, DB, etc) is "the new legacy". And that cloud providers have solved all the pains that Erlang was supposed to address. What's your feeling on this? Elixir sounds very compelling to me, but I worry that I might be going in a direction that's not where the industry is going.

Serverless? You mean vendor lock-in, distribution issues and reproducibility issues, etc?

Yeah. There are obvious downsides, but what if your competitor.manages to outperform you with such tools? That's my concern
Post reply on HN