Just when we thought everything was going well, in 1998, Erlang
was banned within Ericsson Radio AB (ERA) for new product
development. This ban was the second most significant event in
the history of Erlang: It led indirectly to Open Source Erlang and
was the main reason why Erlang started spreading outside Ericsson.
The reason given for the ban was as follows:
The selection of an implementation language implies a more
long-term commitment than the selection of a processor and
OS, due to the longer life cycle of implemented products.
Use of a proprietary language implies a continued effort to
maintain and further develop the support and the development environment. It further implies that we cannot easily
benefit from, and find synergy with, the evolution following
the large scale deployment of globally used languages. [26]
quoted in [12].
In addition, projects that were already using Erlang were allowed to continue but had to make a plan as to how dependence upon Erlang could be eliminated. Although the ban was only within
ERA, the damage was done. The ban was supported by the Ericsson technical directorate and flying the Erlang flag was thereafter not favored by middle management."
And to be completely fair....
"6.2 Erlang in recent times
In the aftermath of the IT boom, several small companies formed during the boom have survived, and Erlang has successfully rerooted itself outside Ericsson. The ban at Ericsson has not succeeded in completely killing the language, but it has limited its
growth into new product areas.
The plans within Ericsson to wean existing projects off Erlang did not materialise and Erlang is slowly winning ground due to a form of software Darwinism. Erlang projects are being delivered on
time and within budget, and the managers of the Erlang projects are
reluctant to make any changes to functioning and tested software.
The usual survival strategy within Ericsson during this time
period was to call Erlang something else. Erlang had been banned
but OTP hadn’t. So for a while no new projects using Erlang were
started, but it was OK to use OTP. Then questions about OTP
were asked: “Isn’t OTP just a load of Erlang libraries?”—and so
it became “Engine,” and so on."
Just when we thought everything was going well, in 1998, Erlang was banned within Ericsson Radio AB (ERA) for new product development. This ban was the second most significant event in the history of Erlang: It led indirectly to Open Source Erlang and was the main reason why Erlang started spreading outside Ericsson.
The reason given for the ban was as follows:
The selection of an implementation language implies a more long-term commitment than the selection of a processor and OS, due to the longer life cycle of implemented products. Use of a proprietary language implies a continued effort to maintain and further develop the support and the development environment. It further implies that we cannot easily benefit from, and find synergy with, the evolution following the large scale deployment of globally used languages. [26] quoted in [12].
In addition, projects that were already using Erlang were allowed to continue but had to make a plan as to how dependence upon Erlang could be eliminated. Although the ban was only within ERA, the damage was done. The ban was supported by the Ericsson technical directorate and flying the Erlang flag was thereafter not favored by middle management."
And to be completely fair....
"6.2 Erlang in recent times
In the aftermath of the IT boom, several small companies formed during the boom have survived, and Erlang has successfully rerooted itself outside Ericsson. The ban at Ericsson has not succeeded in completely killing the language, but it has limited its growth into new product areas.
The plans within Ericsson to wean existing projects off Erlang did not materialise and Erlang is slowly winning ground due to a form of software Darwinism. Erlang projects are being delivered on time and within budget, and the managers of the Erlang projects are reluctant to make any changes to functioning and tested software.
The usual survival strategy within Ericsson during this time period was to call Erlang something else. Erlang had been banned but OTP hadn’t. So for a while no new projects using Erlang were started, but it was OK to use OTP. Then questions about OTP were asked: “Isn’t OTP just a load of Erlang libraries?”—and so it became “Engine,” and so on."
A History of Erlang Joe Armstrong Ericsson AB
©2007 ACM 978-1-59593-766-7/2007/06-ART6
https://lfe.io/papers/%5B2007%5D%20Armstrong%20-%20HOPL%20II...
There's probably a discussion on precisely what this means, but such descriptions as "Erlang is banned" has significant and credible precedent.