[erlang-questions] erlang-questions Digest, Vol 24, Issue 25
Wed May 6 18:48:17 CEST 2009
Well I wouldn't expect you to consume ports. What I meant was to suggest
that it would be enormous, undefeatable win if I could generate what amount
to executables. In that context, one would not expect an interactive
system, ofcoz. What I'm really hoping for, some day, is the ability to make
applications that I can hand out without the user having any idea what
language they were written in.
There's a lot to be said for standalone binaries. Users are dumb and don't
want to learn things. Standalone binaries are one of the major steps
towards opening Erlang up as a general purpose language (along with certain
heresies I'm not talking about yet.)
On Wed, May 6, 2009 at 9:50 AM, Hakan Mattsson <>wrote:
> On Tue, 5 May 2009, John Haugeland wrote:
> > > Work is ongoing in the direction towards a maintainable Standalone
> > (the previous solution from Joe had its good sides but was not easy to
> > > maintain)
> > >
> > You just became my hero, Mr. Lundin <3 Standalone applications would be
> > epic win, _especially_ if they were single executable files.
> We do not attempt to have the runtime system as one single file. But
> we want to be able to have substantially fewer files than today. For
> most applications it will be possible to package them into one file
> per application and load the beam code from that archive. However
> applications that have port programs, device drivers etc. on priv-dir
> will still need to have these file outside the archive file.
> There will be two flavors of standalone applications:
> - The traditional one with a runtime system that is separately
> installed and shared between several of your application(s).
> You can package your application(s) into a single escript file
> and run it without installation if you have setup your paths
> right. Escripts can nowdays contain an archive file with several
> complete Erlang applications. Given that you have installed a
> runtime system, you will be able to ship your applications as one
> single executable escript.
> - A standalone system that containing your application(s) as well as
> the runtime system.
> In both cases, Reltool (which still is experiental) can assist you in
> creating a customized target system that only contains the parts of
> Erlang/OTP that your applications needs and strip away stuff that you
> do not need. For example you may not want to ship source code,
> documentation etc. and you may want to strip away debug info from the
> beam code.
> > This won't be limited to Unix this time around, right?
> No it is not limited to Unix.
> Håkan Mattsson (uabhams)
> Erlang/OTP, Ericsson AB
GuaranteedVPS.com - bandwidth commitments and root starting from $12.98/mo
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions