[erlang-questions] Erlang package manager

Loïc Hoguin essen@REDACTED
Sat Jan 3 19:51:43 CET 2015

On 01/03/2015 07:40 PM, Björn-Egil Dahlberg wrote:
> Well, I know this is a pet peeve for you =)
> I don't think we should let the startup time limit our design choice
> here. I believe the startup time is tightly coupled to loading all the
> modules and then letting the beam-loader transform it. This could
> probably be improved but I don't know how easily. Ideally we would like
> heat up a running beam with all the modules loaded and then dump the
> memory to disk .. appended to some binary, e.g. beam. That should shave
> off some startup time.
> This is however not in the scope of the package manager.

I'm just saying build it as an ELF (or equivalent) instead of a plain 
escript here. There's nothing special to do, it's what you guys have 
done with pretty much everything in the bin/ folder. I'm not sure why 
that should change. :-)

> True, but let's limit this to Erlang applications for starters. Make
> sure we can extend stuff and then take it from there.

All I'm saying is don't work more to prevent people to do things that 
might work for them. No need to put extra checks or things like this. 
The thinking should be Erlang specific but the implementation should not 
enforce that (if possible).

Loïc Hoguin

More information about the erlang-questions mailing list