4 ms·
Kudos for getting this out, and the rationale for adding js support makes sense. This bit: > The pervasive Promise type and the split between synchronous and
by spinningslate 5y ago
Kudos for getting this out, and the rationale for adding js support makes sense. This bit:
> The pervasive Promise type and the split between synchronous and asynchronous functions in JavaScript can be more difficult to learn and use than languages such as Erlang and Go that make no such distinction.
is most interesting to me. I first got interested in Gleam as a statically-typed language targeting the BEAM VM that supported Erlang's concurrency model. Supporting it on JS VMs will be a whole lot harder I'd imagine. Without it, Gleam isn't really that interesting to me on the front end. But if they can pull it off, it gets very interesting. I'd take the Actor / CSP flavour of concurrency over async-await every day of the week.
- lpil 5y agoYes, for sure. I think if you look at Gleam as an alternative to PureScript or similar it's not a very exciting proposition. There's a lot of good options here. This is more an exciting new feature for people who are already using Gleam, they can now do more with the language.