News for hackers. Stuff that matters.

A comment on Securing tomorrow's software: the need for memory safety standards. Parent comment

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.
[ Parent | on HN ]
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-...
[ Parent | on HN ]
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.

[ Parent | on HN ]
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.
[ Parent | on HN ]