The name change came about because we found too many projects named "Lumen" also were launched around the same time or shortly thereafter.
Originally I envisioned a path towards creating a new WASM framework to build web applications using Elixir. Since then LiveView has come out and has made this less of a concern for us. While WASM compilation will be possible and we hope to backfill the runtime needs for web development the real focus and interest in this project for me is...
WASI compilation. With Firefly we will be able build self-contained binaries that will have all (many) of the benefits building applications with the BEAM and distributed systems. If WASI can run on something you should be able to compile your Elixir applications with Firefly and target your desired chipset.
We recently reached a milestone that we are hoping to release a blog post about it in the near future.
Forget WASI, I'm interested in this project as a way to efficiently run Elixir on microcontrollers. It's a great model for embedded programming (not surprising given that was what it was designed).
> The primary motivator for Firefly's development was the ability to compile Elixir applications that could target WebAssembly, enabling use of Elixir as a language for frontend development. It is also possible to use Firefly to target other platforms as well, by producing self-contained executables on platforms such as x86.
[+] [-] bcardarella|2 years ago|reply
A lot has changed since then.
The name change came about because we found too many projects named "Lumen" also were launched around the same time or shortly thereafter.
Originally I envisioned a path towards creating a new WASM framework to build web applications using Elixir. Since then LiveView has come out and has made this less of a concern for us. While WASM compilation will be possible and we hope to backfill the runtime needs for web development the real focus and interest in this project for me is...
WASI compilation. With Firefly we will be able build self-contained binaries that will have all (many) of the benefits building applications with the BEAM and distributed systems. If WASI can run on something you should be able to compile your Elixir applications with Firefly and target your desired chipset.
We recently reached a milestone that we are hoping to release a blog post about it in the near future.
[+] [-] ModernMech|2 years ago|reply
I’ve got bad news…
https://news.adobe.com/news/news-details/2023/Adobe-Unveils-...
[+] [-] xcdzvyn|2 years ago|reply
Have you considered Cranelift as an alternative backend like rustc is doing?
[+] [-] katspaugh|2 years ago|reply
It supports many programming languages.
This new compiler/runtime targets WebAssembly.
[+] [-] chrsig|2 years ago|reply
[+] [-] rahimnathwani|2 years ago|reply
https://news.ycombinator.com/item?id=32703414
[+] [-] rkangel|2 years ago|reply
[+] [-] bmitc|2 years ago|reply
[+] [-] lpil|2 years ago|reply
https://github.com/atomvm/AtomVM
[+] [-] rektide|2 years ago|reply
[+] [-] manveru|2 years ago|reply
> The primary motivator for Firefly's development was the ability to compile Elixir applications that could target WebAssembly, enabling use of Elixir as a language for frontend development. It is also possible to use Firefly to target other platforms as well, by producing self-contained executables on platforms such as x86.
[+] [-] zacksiri|2 years ago|reply
I imagine we would be able to write elixir on the frontend with this.
[+] [-] martin_a|2 years ago|reply
https://www.adobe.com/sensei/generative-ai/firefly.html
[+] [-] greybox|2 years ago|reply
[+] [-] jake_morrison|2 years ago|reply
UI components operate in separate threads and communicate with the back end by sending and receiving async messages.
Back-end components communicate with servers using async messages, then publish results to front-end components.
This is similar to what Joe Armstrong was working on for X-Windows GUIs: https://erlang.org/workshop/2004/ex11.pdf
[+] [-] lmkdgbj|2 years ago|reply
[deleted]