I would appreciate if this post included just a few shell script snippets showing how to replace current Erlang compilation toolchain so Erlang/Elixir/other-BEAM-langs can try it, i.e. a drop-in replacement for your day-to-day dev workflow.

I don't mind compiling `firefly` from source (as the GitHub page instructs). That's all fine and an accepted reality when an experimental tool is starting to take off.

But not providing much of a context + actionable list of items on how to try it in your day-to-day work is to me a PR piece doomed to fall on deaf ears.

This is not an investor pitch to business people. You're advertising to programmers. Please craft your articles accordingly.

Don't get me wrong, I am glad this exists and will follow it. I just wish we had something to copy-paste in our `~/.bashrc` file and and be able to try the tool today.