[HN Gopher] Lumen: Alternative BEAM implementation, designed for...
       ___________________________________________________________________
        
       Lumen: Alternative BEAM implementation, designed for WebAssembly
        
       Author : brainless
       Score  : 134 points
       Date   : 2021-07-31 06:30 UTC (16 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | cryo wrote:
       | Wod, running Erlang/Elixir in the browser would be super awesome.
        
       | sheepdestroyer wrote:
       | Not related to https://docs.unrealengine.com/5.0/en-
       | US/RenderingFeatures/Lu...
        
         | Dragory wrote:
         | Likewise not related to https://lumen.laravel.com/
        
       | cercatrova wrote:
       | See also Gleam, a statically typed functional programming
       | language for the BEAM:
       | 
       | https://gleam.run/
        
         | AlchemistCamp wrote:
         | The vast majority if code that gets used on this will be Erlang
         | and Elixir. At least for now, those are the two languages on
         | the BEAM with traction.
         | 
         | It's interesting to see how Caramel, Gleam, LFE, etc, will
         | develop, though.
        
         | bbzealot wrote:
         | How is this related?
         | 
         | I mean I get it targets the BEAM, but Gleam is a programming
         | language, Lumen is a VM.
        
           | marci wrote:
           | (Not parent) maybe losely related to:
           | https://gleam.run/news/v0.16-gleam-compiles-to-javascript/
        
       | cycomanic wrote:
       | I think it would be really nice to have some description what
       | BEAM actually is. I don't think this is so common knowledge. The
       | issue is also that there are no links even and it's not like BEAM
       | is a very google friendly term. Currently the readme simply
       | assumes that one already knows what lumen is about.
        
         | johnisgood wrote:
         | Search for "BEAM Erlang".
         | 
         | https://blog.erlang.org/a-brief-BEAM-primer/
         | 
         | https://www.youtube.com/watch?v=_Pwlvy3zz9M (Robert Virding -
         | Hitchhiker's Tour of the BEAM)
        
         | brainless wrote:
         | I found this video really good introduction to what BEAM is and
         | allows for programmers:
         | https://www.youtube.com/watch?v=JvBT4XBdoUE&pp=sAQA
        
       | brainless wrote:
       | If I am learning Rust (having a Python, JS/TS background) and am
       | interested in the fault tolerant execution model of BEAM (cheap
       | micro, pre-emptive, "processes"), what Rust crates (libraries)
       | would anyone suggest to get a similar execution model?
        
         | praveenperera wrote:
         | act-zero - https://github.com/Diggsey/act-zero
        
         | alpaca128 wrote:
         | Bastion is aiming for exactly that
        
         | sealeck wrote:
         | Lunatic?
         | 
         | https://lunatic.solutions
        
         | nesarkvechnep wrote:
         | The `actix` crate.
        
       | max_ wrote:
       | What are the technical advantages of having a Wasm based BEAM
       | implementation?
        
         | codetrotter wrote:
         | From pretty far down in the README:
         | 
         | > The primary motivator for Lumen's development was the ability
         | to compile Elixir applications that could target WebAssembly,
         | enabling use of Elixir as a language for frontend development.
        
         | tluyben2 wrote:
         | BEAM is also a very nice VM if you are thinking of a target for
         | your own language. It is easy to learn and use. And this adds
         | more freedom.
        
         | bcardarella wrote:
         | We are hoping for several outcomes. The first is web wasm
         | compilation. We have some ideas on what architectural
         | advantages can come from having BEAM controlled UI. The second
         | is a WASI compilation. So targeting stand alone binaries. This
         | is different than other "compile BEAM to binary"
         | implementations. We are targeting a footprint size of 200kb
         | (web and wasi) which gives Erlang and Elixir an opening to
         | targeting more IoT devices.
        
       ___________________________________________________________________
       (page generated 2021-07-31 23:02 UTC)