Re:Securing tomorrow's software: the need for memory safety ...
by teeray on Wednesday February 26, 2025 @09:20PM
(#43190622)
What is it specifically about the BEAM VM that positions it above, say, Go on K8S?
Re:Securing tomorrow's software: the need for memory safety ...
by BeFlatXIII on Thursday February 27, 2025 @10:02AM
(#43194967)
Not having to learn K8s
Re:Securing tomorrow's software: the need for memory safety ...
by pdimitar on Thursday February 27, 2025 @01:56PM
(#43197278)
Ability to manage tens of thousands of stateful connections without the 95th percentile requests jumping to 5 seconds.
Just to start with.
Re:Securing tomorrow's software: the need for memory safety ...
by Sytten on Wednesday February 26, 2025 @09:51PM
(#43190811)
I get the appeal, but without strong typing it's a no-go in my book. Get me an elixir with proper types and we can talk.
Re:Securing tomorrow's software: the need for memory safety ...
by Nilithus on Wednesday February 26, 2025 @11:16PM
(#43191304)
I believe they have already started this effort. https://elixir-lang.org/blog/2023/06/22/type-system-updates-...
Re:Securing tomorrow's software: the need for memory safety ...
by pdimitar on Thursday February 27, 2025 @01:57PM
(#43197291)
They have but it's mostly a labor of love and it's very difficult to fit a static type system into a dynamically typed language.
We already have some false positives. Happily the team is very motivated and is grinding away at them, for which we the community are forever grateful.
Re:Securing tomorrow's software: the need for memory safety ...
by pdimitar on Wednesday February 26, 2025 @09:56PM
(#43190840)
Oh I agree. The Erlang/Elixir ecosystem is in danger of Rust inventing a BEAM-like runtime and making it irrelevant.
Re:Securing tomorrow's software: the need for memory safety ...
by dudus on Thursday February 27, 2025 @12:16AM
(#43191577)
Elixir is Lisp with sprinkles on top
Re:Securing tomorrow's software: the need for memory safety ...
by BeFlatXIII on Thursday February 27, 2025 @10:03AM
(#43194979)
Lisp for people who hate parentheses.
Re:Securing tomorrow's software: the need for memory safety ...
by pdimitar on Thursday February 27, 2025 @01:58PM
(#43197300)
No, it's LISP for people who understand multicore CPUs exist for a long time now.
Modern LISP dialect authors still believe threads are a super clever idea which is just... /facepalm.
We need the BEAM VM's guarantees, not yesterday but like 20 years ago, everywhere. The language itself does not matter. But we need that runtime's guarantees!