How And Why We Switched from Erlang to Python (2011)

Re:How And Why We Switched from Erlang to Python (2011) by robertAngst on Sunday April 28, 2019 @02:15PM (#19772687)

>Pick a language that has limited programmers, bring programmers from around the country, pay them well beyond 6 figures so they don't leave and have a crisis every time a programmer leaves.

>Go with a mainstream language that they teach every CS kid and has every googable question imaginable in SO, hire 1 experienced programmer to manage a bunch of post-college-kids.

There are lots of good reasons to pick a language with a strong community. Once in a while, I hear people recommend obscure languages(or up-and-coming), and I think- that is going to be expensive to maintain.

[ Parent | on HN ]

Re:How And Why We Switched from Erlang to Python (2011) by kvakvs on Sunday April 28, 2019 @02:19PM (#19772718)

You do not need a large team of Erlang developers though, a much smaller team can hold the project afloat, even hire consultants to fix it and leave it for a few years. Also Erlang dev salaries aren't that stellar, just average what you'd pay a Python or a Java person.

[ Parent | on HN ]

Re:How And Why We Switched from Erlang to Python (2011) by shRaj9fEc8Vith on Monday April 29, 2019 @04:17AM (#19776693)

it's almost impossible to find Erland dev in my country :D

of course we can have someone learn and then teach to the rest of the team but why bother doing that when you can select another language where it's a lot easier to hire

[ Parent | on HN ]