otp
gleam-otp-design-principals
| otp | gleam-otp-design-principals | |
|---|---|---|
| 9 | 1 | |
| 352 | 3 | |
| 11.4% | - | |
| 7.3 | 6.1 | |
| 29 days ago | about 1 year ago | |
| Gleam | CSS | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
otp
-
Learn OTP with Gleam
Modern type system over BEAM sounds great but unfortunately OTP is still not 100% supported https://github.com/gleam-lang/otp?tab=readme-ov-file#limitat...
-
Gleam
They seem to have rewritten/wrapped OTP, but it's not production ready. https://github.com/gleam-lang/otp
YMMV, but a BEAM language without OTP severely limits its appeal and usability.
-
Things I like about Gleam's Syntax
Looks like it is an external library[^1]. Readme states it is experimental and lists some limitations.
[^1]: https://github.com/gleam-lang/otp
-
v0.18 of Gleam, a type safe language written in Rust for the Erlang VM, is out
We have a fully type safe and OTP compatible implementation of actors and supervisors here https://github.com/gleam-lang/otp
-
v0.17 of Gleam, a type safe language written in Rust for the Erlang VM, is out
No primitives as it's not possible to have them when compiling to JavaScript, but we do have them as types and functions in the OTP library https://github.com/gleam-lang/otp
-
gleam/otp syntax error at "if erlang"
On the advice of u/WrongJudgment6 I'm reading the Gleam OTP tests. But I can't compile, and hence can't test, the code. (I'd like to do that so I can tweak the tests to do my own experiments.) Whenever I try I get an error like this:
-
How to learn to use concurrency and/or OTP in Gleam?
And docs at https://hexdocs.pm/gleam_otp/
-
Gleam 0.15 – Type-safe language for the Erlang VM
We have a fully type safe and Erlang compatible OTP library! It is used in production today.
https://github.com/gleam-lang/otp
It is not a wrapper around gen_server etc, but instead it is a full implementation from the ground up using a very small core. This was done because:
a) Erlang OTP cannot be typed, we need different abstractions are designed with types in mind
b) We want to be confident that our abstractions are powerful enough to build something like OTP, rather than cheating by relying on type casts.
I'm very happy with how Gleam OTP is going, but it is not the focus now that an initial version is out. Tooling and documentation is more important at the moment.
gleam-otp-design-principals
-
Gleam
https://github.com/wmealing/gleam-otp-design-principals/blob...
This is what I wrote regarding using otp in gleam. One of the issues I'm working on next is to send typed messages to processes, which has me a little stumped.
At the moment the typed channels work, you can't register () a channel or a pid.
I will likely continue working on this document once I have my current project completed.
What are some alternatives?
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
moor - A rewrite of the classic LambdaMOO server; but in Rust and on a modern tech stack
alpaca - Functional programming inspired by ML for the Erlang VM
riot - An actor-model multi-core scheduler for OCaml 5 🐫
hamler - Haskell-style functional programming language running on Erlang VM.
langs-in-rust - A list of programming languages implemented in Rust, for inspiration.
plug - 🔌 A Gleam HTTP service adapter for the Plug web application interface
messages-rs - Runtime-agnostic actor library
Rustler - Safe Rust bridge for creating Erlang NIF functions
eyg-lang - Experiments in building "better" languages and tools; for some measure of better.
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
Phoenix - Peace of mind from prototype to production