[HN Gopher] Erlang/OTP 27.0 Release Candidate 1
___________________________________________________________________
Erlang/OTP 27.0 Release Candidate 1
Author : lobo_tuerto
Score : 116 points
Date : 2024-02-16 14:34 UTC (8 hours ago)
(HTM) web link (www.erlang.org)
(TXT) w3m dump (www.erlang.org)
| rhodin wrote:
| Most interesting might be the new "tprof"-tool that allows for
| heap profiling
| rozap wrote:
| This will be huge. One of the biggest issues I had running an
| erlang system that moved lots of arbitrary sized, untrusted
| data through it in a parallel way was understanding what was
| going on in the process heaps and reference counted shared
| binary heap. Especially the shared heap since there's no way to
| set an upper bound on it, and when you exceed it the VM
| crashes.
| usr1106 wrote:
| Open Telecoms Platform. Not one-time password. I had to look that
| up.
| cpursley wrote:
| OTP has been around probably longer than you have.
| usr1106 wrote:
| Not true. Erlang is from 1986. I programmed BASIC in 1980 and
| Pascal in 1983.
|
| Of course I have heard Erlang. Wikipedia says Erlang/OTP is a
| synomym. That I managed not to notice for 38 years.
| sodapopcan wrote:
| Essentially a synonym ya. Within the BEAM community when
| people say OTP they often are referring to Erlang's massive
| standard library (which includes stuff like process
| management, a key/value store, a relational database, a
| state machine, and a ton of other goodies) whereas Erlang
| refers to the language itself. Eg, when programming in
| Elixir we use OTP, not Erlang.
| ch4s3 wrote:
| OTP doesn't mean Open Telecoms Platform anymore. Yes it's on
| Wikipedia because that was the historical name and use case,
| but the Erlang maintainers and the ecosystem foundation the EEF
| refer to it simply as OTP, Erlang's standard library.
|
| From Erlang's website:
|
| >OTP is set of Erlang libraries and design principles providing
| middle-ware to develop these systems. It includes its own
| distributed database, applications to interface towards other
| languages, debugging and release handling tools.
| IceDragon200 wrote:
| I think the most exciting part is the new documentation format,
| as someone who primarily works in elixir, I do reference the
| erlang standard library every now and then so an easier and
| familiar documentation format is welcomed.
|
| I just hope that "h :ets" works in iex later (for those who don't
| know, it shows the help/module/function documentation of the
| value specified)
| wut42 wrote:
| That was implemented since OTP 24, in 2018, and works fine in
| iex already.
|
| https://www.erlang.org/doc/apps/kernel/eep48_chapter
|
| https://www.erlang.org/eeps/eep-0048.html
|
| https://github.com/elixir-lang/elixir/issues/7198
| gregors wrote:
| I'm curious what the default memory usage will be with the
| raising of the default process limit to 1_048_576?
|
| I think it's a good move, if nothing else people who do
| benchmarks with 1 million processes but don't know those settings
| are changeable will get further.
| tiffanyh wrote:
| For an ecosystem as large as Erlang/OTP, it actually has
| surprising little investment relative to its size.
|
| An area impacted the most, is R&D into improving raw performance.
|
| It's effectively just Lukas Larsson & Bjorn Gustavsson trying to
| solve this problem for the past _10-years_ or more.
|
| Their work is hugely appreciated, yet they get little to no
| support on this front.
|
| It's definitely beyond my technical abilities to help, but I
| would financially sponsor focus in this area.
|
| Does anyone know how I can donate/sponsor more focus on improving
| raw performance?
| sahruum9 wrote:
| I don't have a direct answer for you, but the Erlang Ecosystem
| Foundation seems like a good place to start.
|
| https://erlef.org/
| jacquesm wrote:
| > It's definitely beyond my technical abilities to help
|
| I think this goes for most people that would like to help. This
| is very mature code and ripping out any portion and replacing
| it without a massive amount of groundwork isn't going to fly,
| Erlang is used for semi-realtime mission critical stuff all
| over the globe. That's 'tread very carefully' ground.
| waynesonfire wrote:
| congrats on another awesome release. such an incredible runtime
| system. I keep solving the same problems with half assessed
| solutions that I would otherwise get for free from Erlang.
| troupo wrote:
| Nice to see cross-pollination between Erlang and Elixir
| dlachausse wrote:
| Reading the change logs speaks volumes to the maturity of this
| ecosystem. A lot of really great quality of life improvements
| here and the always welcome performance improvements.
|
| Congratulations and thank you to everyone involved!
| pjmlp wrote:
| Nice to see JIT improvements.
___________________________________________________________________
(page generated 2024-02-16 23:02 UTC)