Hi Mazen,<br>We will attempt to do so. A number of things went into our decision, not just reliability. There was the scaling up of concurrent connections issue, since some of the functionality in the workgroup application involves a lot of "comet-like" scenarios.
<br><a href="http://en.wikipedia.org/wiki/Comet_(programming)">http://en.wikipedia.org/wiki/Comet_(programming)</a><br>Another factor was stack simplification. <br><br>To your point, even the reliability issue is very important, in the context of erlang we liked the fact that
<br>we could "add reliability" without having to do significant re-architecting of the product. In other words, you could<br>use erlang in the most crappy way, and achieve no reliability -- then hire an OTP guru and reuse a lot of work, putting it into
<br>better frameworks/patterns. Certainly easier than doing it with ruby or python code..<br><br>Not being complete novices in Erlang, we took care of some important things like making sure the problem space <br>was partitioned properly, so that Mnesia can scale effectively..we'll talk about that in part two.
<br><br>Regards,<br>Vijay<br><br><br><div><span class="gmail_quote">On 4/19/07, <b class="gmail_sendername">Mazen</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>When you continue in the next post, you should include _how_ you used Erlang. Personally I think it is great that you achieve great reliability using Erlang but you could also use Erlang in the most crapy way as well and achieve... well... no reliability (YES believe it or not! :P)
<br><br>So in other words... when you tell us if Erlang lived up to your expectations, let us know how and in which parts it was used. Looking forward to it, I think the idea is great! No more pisky comments about "But this is in powerpoint!, I can't read that!" :)
<br><br>/Mazen<br><br><br>Guest wrote:<br>Hi All,<br>We are a recent startup from the Bay Area that launched a service that tries to bridge PowerPoint and Web 2.0,<br>making it easy to collaborate, distribute, and utilize PowerPoint in a group context. We recently started blogging,
<br>and some of our blog posts are going to be on why we chose Erlang in a startup context.<br>We would love any thoughts/comments/feedback from Erlang users..<br><br>Our first blog post on this is entitled: From Python to Ruby on Rails to Erlang..
<br><br><a href="http://slideaware.typepad.com/slideaware/2007/04/from_python_to_.html">http://slideaware.typepad.com/slideaware/2007/04/from_python_to_.html</a> (<a href="http://slideaware.typepad.com/slideaware/2007/04/from_python_to_.html">
http://slideaware.typepad.com/slideaware/2007/04/from_python_to_.html</a>)<br><br><br>In the next few weeks we plan to write up more articles, as well as release some erlang code that<br>could (hopefully!) be useful to others.
<br><br>I apologize if this is considered off-topic/advertising. Our intent here is to help others realize that<br>Erlang is a source of competitive advantage to startups, especially in the web 2.0 context<br>(concurrency for us is more important than latency).
<br><br>Regards,<br>Vijay<br><br><br> Post recived from mailinglist<br>(end of quote)<br><br>_________________________________________________________<br>Post sent from <a href="http://www.trapexit.org">http://www.trapexit.org
</a><br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:firstname.lastname@example.org">email@example.com</a><br><a href="http://www.erlang.org/mailman/listinfo/erlang-questions">