<br><div class="gmail_quote">On Fri, May 22, 2009 at 2:04 PM, Steve Davis <span dir="ltr"><<a href="mailto:steven.charles.davis@gmail.com">steven.charles.davis@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I could not agree more with Joe's comment about non-functional being<br>
basically ignored for much too long during development!<br>
<br>
However, I'm kind of intrigued as to what answers to the questions<br>
posed would in practice yield an answer *other than* Erlang/OTP?<br>
<br>
The only one that works for me is: "I'm being forced to use framework<br>
'X' against my better technical judgement"<br>
<br>
I'd be interested in what others think about this.<br>
<br>
/s<br>
(yep, I'm still drinking the Kool-Aid, and seeing no reason as yet to<br>
stop :))<br>
<div class="im"><br>
<br>
On May 22, 9:17 am, Joe Armstrong <<a href="mailto:erl...@gmail.com">erl...@gmail.com</a>> wrote:<br>
> You have to tell us more about your problem in order to get sensible<br>
</div>> feedback. So far you have said...<br>
<div><div></div><div class="h5">_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://www.erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://www.erlang.org/mailman/listinfo/erlang-questions</a><br>
</div></div></blockquote></div><br>Well, as has been mentioned, you could go with clojure and terracotta for the JVM; Clojure is a lisp-variant without destructive updates and comes with transactional memory built-in; it's thus functional, benefits from a two-way communication system with the java libraries, can be good at concurrency. Terracotta would let you distribute the code with relatively enough ease too.<br>
<br>Hot code swapping can be substituted by updating nodes one by one and a good switching system; with enough isolation, the update becomes transparent and requires no downtime at all, while forcing you to keep redundancy in mind.<br>
<br>It's certainly more complicated to set up as a distributed environment, but it's a completely acceptable alternative, especially for the libs and the lisp macro system.<br>