Re:How And Why We Switched from Erlang to Python (2011)
by oconnor663 on Sunday April 28, 2019 @02:30PM
(#19772785)
I think Facebook chat had a very similar experience. The first version was written by someone who liked Erlang. Later on, when some performance issues came up (probably related to GC), no one knew Erlang, and all the high performance backend code in the company was in C++. So it made sense to rewrite the thing.
[ Parent
| on HN ]
Re:How And Why We Switched from Erlang to Python (2011)
by trab on Sunday April 28, 2019 @03:12PM
(#19773059)
Then they acquired whatsapp that was written in Erlang.
Re:How And Why We Switched from Erlang to Python (2011)
by ludwigvan on Sunday April 28, 2019 @03:40PM
(#19773219)
And I think I had read that Whatsapp used Erlang because Facebook Chat was using Erlang and they thought Facebook knew what they were doing and decided to use the same tech. What a twist
Re:How And Why We Switched from Erlang to Python (2011)
by reducesuffering on Sunday April 28, 2019 @04:11PM
(#19773391)
Where did you read that? I believe Whatsapp used erlang because they leveraged ejabberd [0] for XMPP. Wouldn't surprise me if this is why FB originally used Erlang for the chat servers too.
[0] https://en.wikipedia.org/wiki/Ejabberd
Re:How And Why We Switched from Erlang to Python (2011)
by darkr on Sunday April 28, 2019 @04:40PM
(#19773538)
Yep. Facebook chat was originally based on ejabberd.
Source: https://web.archive.org/web/20121224094022/http://cufp.galoi...
Re:How And Why We Switched from Erlang to Python (2011)
by fineoldcannibal on Sunday April 28, 2019 @11:06PM
(#19775522)
I believe it was because of the Beluga acquisition which was in Erlang