4 ms·
Nope, Elixir for backend. We need the BEAM VM's guarantees, not yesterday but like 20 years ago, everywhere. The language itself does not matter. But we need t
by pdimitar 2y ago
Nope, Elixir for backend.
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!
- teeray 2y agoWhat is it specifically about the BEAM VM that positions it above, say, Go on K8S?
- BeFlatXIII 2y agoNot having to learn K8s
- pdimitar 2y agoAbility to manage tens of thousands of stateful connections without the 95th percentile requests jumping to 5 seconds. Just to start with.
- Sytten 2y agoI 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.
- pdimitar 2y agoOh I agree. The Erlang/Elixir ecosystem is in danger of Rust inventing a BEAM-like runtime and making it irrelevant.
- Nilithus 2y agoI believe they have already started this effort. https://elixir-lang.org/blog/2023/06/22/type-system-updates-research-dev/ https://elixir-lang.org/blog/2023/06/22/type-system-updates-...
- pdimitar 2y agoThey 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.
- dudus 2y agoElixir is Lisp with sprinkles on top
- BeFlatXIII 2y agoLisp for people who hate parentheses.
- pdimitar 2y agoNo, 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.