3 ms·
Gleam doesn't have macros, which many Elixir libraries (such as Phoenix and Ecto) uses to great effect. Gleam for example has issues with verbosity of decoding
by lawn 4mo ago
Gleam doesn't have macros, which many Elixir libraries (such as Phoenix and Ecto) uses to great effect.
Gleam for example has issues with verbosity of decoding/encoding json whereas in Rust you derive serde and in Elixir it's just a function call away.
Elixir has a more mature ecosystem. While you can for example use Phoenix with Gleam (or some other Gleam framework) the experience just isn't the same.
The big draw with Gleam over Elixir is the typing (where Elixir is now closing the gap) and being able to compile to JavaScript (which is also what Hologram is doing for Elixir).
I prefer Gleam's typing system and the Rust-like syntax, but for now I feel Elixir is the better choice for all my web dev projects.
- rapnie 4mo ago> and being able to compile to JavaScript Apparently it is not that difficult to add different compiler backends. There was a presentation [0] recently about adding wasm support as a compiler target. The implementation was quite far along, including support for the wasm component model. [0] https://www.youtube.com/watch?v=UQ0--ODjiDk https://www.youtube.com/watch?v=UQ0--ODjiDk
- _danielle_ 4mo agoJust to add a slight correction here, support for the wasm component model wasn't added in the target I wrote
- rapnie 4mo agoThat was a misunderstanding then, thank you for correcting.