gleam
purerl
Our great sponsors
gleam | purerl | |
---|---|---|
92 | 6 | |
13,924 | 305 | |
58.7% | 4.3% | |
9.9 | 5.9 | |
5 days ago | 3 months ago | |
Rust | Haskell | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
gleam
- Cranelift code generation comes to Rust
-
Inko Programming Language
I had been only following this language with some interest, I guess this was born in gitlab not sure if the creator(s) still work there. This is what I'd have wanted golang to be (albeit with GC when you do not have clear lifetimes).
But how would you differentiate yourself from https://gleam.run which can leverage the OTP, I'd be more interested if we can adapt Gleam to graalvm isolates so we can leverage the JVM ecosystem.
-
Switching to Elixir
I don't think the implementation itself is at fault, but yes, I do think that the design of dialyzer makes it an (at times) faulty type checker. The unfortunate reality of a type checker that fails sometimes is that it makes it mostly useless because you can never trust that it'll do the job.
To be clear, I've had it fail in a function where I've literally specced that very function to return a `binary` but I'm returning an `integer` in one of the cases. This is a very shallow context but it can still fail. Now add more functions, maybe one more `case`.
I think an entire rethink of type checking on the BEAM had to be done and that's why eqWalizer[0] was created and why Elixir is looking to add an actual sound, well-developed type checker. Gleam[1] I would assume is just a Hindley-Milner system so that's completely solid. `purerl`[2] is just PureScript for the BEAM so that's also Hindley-Milner, meaning it's solid. `purerl` has some performance issues caused by it compiling down to closures everywhere but if you can pay that cost it's actually pretty fantastic. With that said my bet for the best statically typed experience right now on the BEAM would be `gleam`.
- Gleam
- Unpacking Elixir: Resilience
-
Erlang/OTP 26.1 Released
If you don’t like the syntax highly recommend giving https://gleam.run a try
-
Elixir for Cynical Curmudgeons
If you're a fan of the ecosystem, but not of dynamic types, there are statically typed languages on BEAM, eg Gleam (https://gleam.run/)
-
Async rust – are we doing it all wrong?
Keep an eye on gleam lang if you’re not already. It’s a language with an ML inspired type system (like rust) that compiles to erlang. It is likely too nascent to be used in production (in terms of tooling, ecosystem, stability, etc).
- I hereby officially announce the Elixir type system effort is into development
purerl
-
Erlang: The coding language that finance forgot
I will put in a good word for PureScript for the beam with `purerl`. It's my go-to for writing BEAM code nowadays. Notably PureScript tooling including LSP, package management, etc., just works, so you are able to just get to work in internalizing the way OTP and other Erlangy things are expressed in a statically typed, pure language.
https://github.com/purerl/purerl & https://purerl-cookbook.readthedocs.io/ for more information. Join the PureScript discord and the #purerl channel if you want help.
-
purerl - Integrating PureScript into Elixir projects
purerl is a compiler for turning PureScript code into Erlang code, so that you're able to write BEAM (the Erlang virtual machine) applications using it.
-
Phoenix 1.7 is View-less
You've been able to write PureScript that compiles to Erlang and has perfect interop for years, via `purerl`[0]. Using it with Elixir is as simple as adding `purerlex` as a compiler and having your PureScript code automatically compile when `mix` compiles things, and off you go.
In terms of the typing itself, it's exactly what you get in all of PureScript, strict static typing with no `any` or the like. Using `Pinto`, the de facto OTP layer in PureScript your processes are typed, i.e. their `info` messages & state are typed, which means that they are all much more like strongly typed state machines than anything else.
You can see an example of a basic `gen_server` here:
The differences aren't very big in terms of what you'd expect to be doing. One small thing to note is that the `GenServer.call` expects a closure to be passed instead of having the split between `gen_server:call` & `handle_call`, removing the need for synchronizing two places for your messages being sent and handled.
- Angular without SSR is faster than Next.js with SSR. I have the data
- Beam VM Wisdoms
- V0.14 of Gleam, a type safe language for the Erlang VM, has been released
What are some alternatives?
are-we-fast-yet - Are We Fast Yet? Comparing Language Implementations with Objects, Closures, and Arrays
web3.js - Collection of comprehensive TypeScript libraries for Interaction with the Ethereum JSON RPC API and utility functions.
Rustler - Safe Rust bridge for creating Erlang NIF functions
nx - Multi-dimensional arrays (tensors) and numerical definitions for Elixir
ponyc - Pony is an open-source, actor-model, capabilities-secure, high performance programming language
hamler - Haskell-style functional programming language running on Erlang VM.
Gradualizer - A Gradual type system for Erlang
otp - 📫 Fault tolerant multicore programs with actors
lumen - An alternative BEAM implementation, designed for WebAssembly
haskell-language-server - Official haskell ide support via language server (LSP). Successor of ghcide & haskell-ide-engine.