[erlang-questions] OT: Programming Language Selection as a Business Strategy

Perrog perrog@REDACTED
Sun Apr 15 00:31:41 CEST 2007

I'm new to this list, but I found this thread quite intresting...

2007/4/14, Ulf Wiger <ulf@REDACTED>:
> It's probably more accurate to say that Erlang was developed in an Ericsson
> laboratory in response to a perceived technology need. Bjarne Däcker's
> thesis gives some good background on this:
> It also mentions that Erlang was banned in 1998, due to perceived business
> needs.

Does this mean Erlang should be avoided outside Ericsson's CS-lab as
much as possible? :-)

2007/4/14, Ulf Wiger <ulf@REDACTED>:
> I agree with Thomas that essays like "beating the averages" give an
> interesting angle on this question. Large companies will also worry about
> the cost of diversity and lock-in effects. This is most likely much less of
> a problem in small companies.
> For large companies, aspects that will have measurable consequences
> include: [E.N. Cost of training support staff... Difficulty... Re-training costs...
> Difficulty...Difficulty... expensive redesign.
> ... wouldn't you want to try to eliminate the above challenges, if possible? —end of E.N.]

Who said this only concern large companies...?

In addition to all aspects above, mainstream languages usually comes
with a large library (e.g. .Net/WinFX) and special designed tools
(e.g. Visual Studio.)

If problems becomes more transparent if solved in Erlang, what are
these type of problems really? What kind of Design Patterns make
Erlang beat the average?


More information about the erlang-questions mailing list