• autokludge
      link
      English
      7
      edit-2
      3 months ago

      While having a quick look through old news:

      From June 2021 (v0.16) (https://gleam.run/news/v0.16-gleam-compiles-to-javascript/#how-does-it-work)

      Much like the Erlang compiler backend this new JavaScript backend outputs human readable and pretty printed source code. It is now included with the compiler and does not require any extra components to be installed to use it.
      Rather than attempting to replicate a subset of Erlang’s actor model Gleam uses the standard promise based concurrency model when targeting JavaScript. While this may be disappointing for some, it means that there is no additional runtime code added. This keeps bundle size small and makes it so code written in Gleam can be called like normal from languages such as JavaScript and TypeScript.

      Jan 2024 v0.34 (https://gleam.run/news/v0.34-multi-target-projects/#multi-target-projects) mentions some additional work done to enable multi target projects such as Lustre

    • @[email protected]
      link
      fedilink
      23 months ago

      The guide/tutorial has some specifics about things that are allowed in erlang vs js. There’s a few features that don’t work completely in one or another.

  • TehPers
    link
    fedilink
    English
    73 months ago

    Everytime I see a post about this, I end up confusing it with gleam.io (which is a popular service for people doing giveaways). Looks cool, just the naming conflict is unfortunate.

  • @[email protected]
    link
    fedilink
    -43 months ago

    Another BEAM language. This one has (some?) static typing, and (bleach) JavaScript -like syntax. Is there a tldr of why write another of these instead of using an existing one? There are already a few. Even a port of typescript to beam might be a good approach. I agree with the concept of a typed functional language on BEAM but this doesn’t look attractive. I liked PureScript in the JS world but I think it lost out to typescript.