[erlang-questions] Re: Benchmarks

[Isaac Gouy]

--- On Wed, 1/13/10, Joe Armstrong <erlang@REDACTED> wrote:
-snip-
> Erlang was designed to provide an off-the-shelf solution to
> all the
> things we needed to do to build a fault-tolerant, soft
> real-time
> distributed telephone switch control software with hot code
> replacement.
> 
> Erlang was not designed to be as fast as C at doing things
> that C is good at.


That's pretty much what the Erlang FAQ says..



-snip- 
> Increasing the pressure to use Erlang just increases the
> reasons why
> you should not use Erlang - the technical arguments just
> get more and
> more intense, and you're still in equilibrium..
> 
> To convince anybody to use Erlang you have to break the
> equilibrium.
> 
> Instead of increasing the pressure try reducing the
> resistance.
> 
> In my experience most resistance is due to non-spoken
> non-technical
> reasons.  The primary reason is usually fear of
> failure (FOF). FOF is
> a very strong motivating force.
> 
> One excellent method of reducing FOF is tell "success
> stories" - tell
> 'em about the successful Erlang projects - how quickly they
> wrote the
> code how quickly they crushed the opposition, the great
> amounts of
> money they made (:-)). Tell them about the failures that
> using *some
> other language* had in similar circumstances.
> 
> Perhapse the project will fail if they do not use Erlang,
> and
> what if the opposition does it in Erlang before us and
> we're bankrupt ...
> there's a thought ...
> 
> People like stories, so tell then stories of Erlang
> successes - this
> will reduce FOF.


Yes.