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

81–90 of 125 posts

Re: Erlang/OTP 25.0 Release

#81

Post by ricketycricket »

melony wrote: post #62
isaacimagine wrote: post #53

Earlier quoted context omitted.

To that end, cloud platforms like fly.io[0] provide first-class support for Erlang/Elixir and related frameworks. If the industry is converging on Erlang-like solutions, it makes sense that Erlang is a natural fit. [0]: https://fly.io/phoenix-files

Problem is that outside of Fly, somebody still has to do the system admin. Erlang (used in an web application context) won't manage itself no matter how well designed it is. Stuff like serverless is meant to completely outsource DevOps.

I mean, `mix phx.gen.release --docker` generates a nice dockerfile for packaging up a release (which is all Fly does). At that point it's essentially no different than any other containerized application. I've shipped Elixir apps to Heroku, Fly, Render, and Azure with basically no devops on my part.

Re: Erlang/OTP 25.0 Release

#82

Post by jimbob45 »

haolez wrote: post #26

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 works super well for getting off the ground but the goal is to grow big enough that it’s no longer the best option, no?

Just because the industry is willing to waste money on tech they’ve outgrown doesn’t mean you need to.

Re: Erlang/OTP 25.0 Release

#83

Post by conradfr »

Kototama wrote: post #70
sergiomattei wrote: post #48

Is Elixir running on OTP 25?

Not yet, you can use OTP23 or OTP24 at the moment with latest Elixir 1.13. Check https://hexdocs.pm/elixir/1.13/compatibility-and-deprecation...

Although changelog says:

> v1.13.4 (2022-04-07) > This release has been verified to work with Erlang/OTP 25 RC2.

Re: Erlang/OTP 25.0 Release

#84

Post by ricketycricket »

Kototama wrote: post #70
sergiomattei wrote: post #48

Is Elixir running on OTP 25?

Not yet, you can use OTP23 or OTP24 at the moment with latest Elixir 1.13. Check https://hexdocs.pm/elixir/1.13/compatibility-and-deprecation...

1.13.4 is verified on OTP 25 RC2, so I'd assume it supports the release OTP 25.

See: https://github.com/elixir-lang/elixir/releases/tag/v1.13.4

Re: Erlang/OTP 25.0 Release

#85

Post by distortedsignal »

Having worked with erlang for some time now, https://www.erlang.org/eeps/eep-0049 is _very exciting_ to me. One of the issues that I have with the codebase that I'm in is deep nesting, which could be solved with this feature. Very compelling.

(HN mods: feel free to delete this comment or my comment at https://news.ycombinator.com/item?id=31426002, since they're the same content)

Re: Erlang/OTP 25.0 Release

#86

Post by Kototama »

conradfr wrote: post #83
Kototama wrote: post #70

Earlier quoted context omitted.

Not yet, you can use OTP23 or OTP24 at the moment with latest Elixir 1.13. Check https://hexdocs.pm/elixir/1.13/compatibility-and-deprecation...

Although changelog says: > v1.13.4 (2022-04-07) > This release has been verified to work with Erlang/OTP 25 RC2.

Ah nice, I missed that!

Re: Erlang/OTP 25.0 Release

#87

Post by barkerja »

distortedsignal wrote: post #85

Having worked with erlang for some time now, https://www.erlang.org/eeps/eep-0049 is _very exciting_ to me. One of the issues that I have with the codebase that I'm in is deep nesting, which could be solved with this feature. Very compelling. (HN mods: feel free to delete this comment or my comment at https://news.ycombinator.com/item?id=31426002 , since they're the same content)

This is great. I hope this finds its way to Elixir land.

Re: Erlang/OTP 25.0 Release

#88

Post by di4na »

tiffanyh wrote: post #32

With the JIT foundation now set in Erlang/OTP 24 & 25, I can only hope that we'll begin to see massive perf improvement in Erlang/OTP 26. (Thanks you to Lukas and all others who work on this)

I mean we already got a stable 25% or more improvement, to the point that Jason is faster than NIF based json library... we already saw massive perf improvement with the JIT

Re: Erlang/OTP 25.0 Release

#89

Post by di4na »

Thanks to the EEF for funding my work on the float to string algorithm!

And also, if you wonder if you could do it for your current platform of choice, please do not engage. Inside float to string conversion lies madness...

Re: Erlang/OTP 25.0 Release

#90

Post by jlouis »

haolez wrote: post #26

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.

While Serverless does address some of the points which were the design goals of Erlang, it doesn't address them all. In no particular order:

Hardware interaction is more or less non-existent in the world of Serverless.

Timing/Latency is not really controllable. It's at the whim of your provider.

FaaS doesn't support very large systems well. It's far more about scaling down than up.

Erlang is functional for a reason: it minimizes faults. Quality follows.

Complex feature interaction is limited in the stateless serverless world.

Cloud providers tend to solve for a different set of problems, which is fine. But I'm going to claim that many of the things Erlang was designed to solve runs dual to the problems in the cloud space.

Post reply on HN