[erlang-questions] Rather not - aintiquated build/deploy processes (Re: Why isn't erlang strongly typed?)

Taavi Talvik taavi@REDACTED
Tue Oct 21 19:10:38 CEST 2008

On Oct 21, 2008, at 6:12 PM, Holger Hoffstaette wrote:
> Unfortunately this and the rather antiquated build/deploy processes  
> are
> really big (and unnecessary) inhibitors to more widespread adoption -
> which is a shame, because the platform itself is solid and has a lot  
> to
> offer.

Erlang has enourmously strong foundation for build&deploy processes.
- hot code loading
- code replacement at runtime
- erl_boot_server(3)
- remote code loading
- platform independent .beam format (almost, native depends on  
- release_handler(3)

Remeber, this is only foundation and geared towards application
domain of building reliable servers.

For other domains, different build&deploy strategies fit better:
- http://cean.process-one.net/
- http://www.trapexit.org/Maven_and_Erlang

best regards,

More information about the erlang-questions mailing list