top | item 37637702 (no title) lkurusa | 2 years ago https://gleam.run/ Gleam is super promising. discuss order hn newest bryanrasmussen|2 years ago why would you use Gleam instead of Elixir, is there any benefit to using both of them? victorbjorklund|2 years ago The benefits would be if you prefer gleam:s syntax and static typing. In the end all compile down to the same Erlang byte code that runs on the BEAM so neither has any performance benefits. bryanrasmussen|2 years ago ah ok, reading more compiles to JavaScript, generates typescript definitions, can reuse code from all Beam supported languages.So maybe Gleam as an easier way to integrate JS and Erlang / Elixir?
bryanrasmussen|2 years ago why would you use Gleam instead of Elixir, is there any benefit to using both of them? victorbjorklund|2 years ago The benefits would be if you prefer gleam:s syntax and static typing. In the end all compile down to the same Erlang byte code that runs on the BEAM so neither has any performance benefits. bryanrasmussen|2 years ago ah ok, reading more compiles to JavaScript, generates typescript definitions, can reuse code from all Beam supported languages.So maybe Gleam as an easier way to integrate JS and Erlang / Elixir?
victorbjorklund|2 years ago The benefits would be if you prefer gleam:s syntax and static typing. In the end all compile down to the same Erlang byte code that runs on the BEAM so neither has any performance benefits.
bryanrasmussen|2 years ago ah ok, reading more compiles to JavaScript, generates typescript definitions, can reuse code from all Beam supported languages.So maybe Gleam as an easier way to integrate JS and Erlang / Elixir?
bryanrasmussen|2 years ago
victorbjorklund|2 years ago
bryanrasmussen|2 years ago
So maybe Gleam as an easier way to integrate JS and Erlang / Elixir?