<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Nobody has been fired for choosing Java.<br>
<br>
See Mike Williams slides from the London Erlang Factory 2011:<br>
<a class="moz-txt-link-freetext" href="http://www.erlang-factory.com/conference/London2011/speakers/MikeWilliams">http://www.erlang-factory.com/conference/London2011/speakers/MikeWilliams</a><br>
<br>
Digging a bit deeper it comes down to risk management and most big
companies has a strong dislike for anything new and different since
that reeks risk to them. <br>
Take a look at all the start-ups in the US that is using Erlang and
asking for Erlangers. There Erlang has been chosen since it is the
right fit for the problem at hand.<br>
<br>
For a big company with a lot of legacy Java code and people trained
in Java it is far from obvious that a switch to Erlang will be the
right choice. I would actually get a bit nervous if management
accepted such a shift without a thorough investigation and even if
that investigation gave a go-ahead to do a shift I would be nervous
since such a fundamental break with the past only happens when a
company is staring into the abyss of a pending bankruptcy!!<br>
<br>
I was one of the two guys behind a product made in Erlang in
Motorola. One of the main reasons for getting the go-ahead to that
project was that we were building a new product and did not have to
throw anything out. <br>
Eventually we shipped the product as a beta to a single customer,
but the reluctance to bet on something as strange as Erlang for a
"real" contract is still around and I will actually bet on the final
product being written from scratch in C or Java since that is what
the managers and old school architects feel most at ease with!<br>
<br>
The history of technology is full of this kind of stories... and one
day some new technology will come along and overturn whatever
kingdom Erlang might have build. The circle of life continues.<br>
<br>
Cheers,<br>
Torben<br>
<br>
On 11/3/12 18:09 , Shahrdad Shadab wrote:
<blockquote
cite="mid:CADy_4ewi_mb0N5=UiyoJCYC+uuSaGbW3c5W4zx--FmXNFmnj8Q@mail.gmail.com"
type="cite">When I was learning Erlang and understanding its
capabilities I really cannot find a satisfactory answer to the
question that <br>
why in North America companies like former BEA, former Sun, Oracle
, ... use Java to build commercial application servers instead of
Erlang?<br>
From technical perspective such decision doesn't make any sense to
me for following reasons:<br>
<br>
_Java is not a fault tolerant.<br>
_Java performance is nowhere near Erlang.<br>
_Concurrent programming in Java is a pain.<br>
_J2ee Technology introduced as add on to java to make
communication cross servers possible (i.e web services XML
SCHEMA, WSDL) is unreasonably and grotesquely complicated. (This
complication is dictated by the technology and not by the problem
domain)<br>
_Java is not distributed language (No asynch communication is
possible without JMS, also RMI stub solution is more complicated
than it should be).<br>
<br>
and many more reasons I can list here. <br>
<br>
Thanks in advance<br clear="all">
Shahrdad<br>
-- <br>
Software Architect & Computer Scientist<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/torbenhoffmann">http://www.linkedin.com/in/torbenhoffmann</a></pre>
</body>
</html>