<story><title>Bakeware: Compile any Elixir application into a single binary</title><url>https://github.com/bake-bake-bake/bakeware</url></story><parent_chain></parent_chain><comment><author>sergiomattei</author><text>I&amp;#x27;m glad Bakeware is applying brainpower to the entry point problem for simple scripts.&lt;p&gt;I&amp;#x27;m currently learning Elixir and the biggest initial hurdle was how to actually create an application. Most tutorials teach you through iex but rarely how to actually write a running program or library.&lt;p&gt;Things like &amp;quot;mix run&amp;quot; wouldn&amp;#x27;t work until I created an app with mix new, then I had to visit the rabbit hole of genservers and supervisors, etc...&lt;p&gt;It&amp;#x27;s a little complex for beginners and could use some polishing. I can&amp;#x27;t say that I truly understand it still.</text></comment>
<story><title>Bakeware: Compile any Elixir application into a single binary</title><url>https://github.com/bake-bake-bake/bakeware</url></story><parent_chain></parent_chain><comment><author>jart</author><text>Can the cpio command extract the Erlang VM from these binaries? If not, then it shouldn&amp;#x27;t be called cpio. Operating systems have been known to block binaries that have compressed binaries inside them using novel formats tools don&amp;#x27;t understand. The design here is very similar to ZIP, which would be a good thing to consider, since that would grant the end user the flexibility to copy the app out of the bakeware shell into their existing Erlang install without having another Erlang get installed.</text></comment>