[erlang-questions] Good reason for not using "releases"?
Mon Oct 20 23:50:12 CEST 2008
My take would be that if you don't need a facility, don't bother
implementing it. You might find you need releases at some point in
the future, but assuming you don't exclude the possibility of building
them in later (e.g. by writing your code in such a way that prevents
it from happening), then it seems you could add it in if/when the
requirement becomes apparent.
As an analogy, I like to think of myself as someone who tries to
improve their coding skills as far as I'm able, and I think I'm doing
that month by month. That said, I've got no problem building quick
and dirty one-off Perl scripts to e.g. read in some data and reformat
it for me - trying to create elegant code isn't a priority in this
instance, but getting it done as quickly as possible often is a
priority in this case.
I'll be interested to hear what others think
2008/10/21 Kevin <q2h46uw02@REDACTED>:
> Hello, I'm building my first erlang server program, and I've worked my way up from modules, to gen_server and gen_fsm, to supervisor, to application behavior.
> If this application is going to run on a linux host, and boot using a linux init script, does it make sense to take it to the next level of "release", or is that just more complication I don't need to deal with.
> I don't ever anticipate the need for hotswapping of code. The users will have no issues with just restarting the entire thing just like all the other stuff running from init scripts, and they might find hotswapping, or whatever fancy stuff releases offers, more work than appreciated.
> I also don't anticipate this application sharing an running erlang system with any other erlang applications.
> Thanks, especially if this is such an ignorant question.
> erlang-questions mailing list
More information about the erlang-questions