3 ms·

> I don't really see a compelling reason to switch to it from Elixir/Erlang. What about ease of growing your team and finding 3rd party libraries so you don't

> I don't really see a compelling reason to switch to it from Elixir/Erlang. What about ease of growing your team and finding 3rd party libraries so you don't have to re-invent the wheel?

MCRed 12y ago
I think it's funny, but not surprising, that you assume it will be easier to grow the team with Go. It's not a more popular or established language, yet. But also, I've recently built a team using Elixir before Elixir was even 1.0. About the hardest possible example of that argument and we found great people, grew a great team in Austin Texas. Having a really good language as part of your stack works as a filter-- you get the best programmers that way. Not saying go is bad, but it's popular, and so you're going to get a lot of people who chose it because it was popular. As for re-inventing the wheel, erlang has a lot of 3rd party libraries, and is ahead of go in that regard, for the time being. Most interesting to me is your perception of the situation, which I'm guessing is driven by the fact that go is very popularly being evangelized right now.
- eropple 12y ago
  > Having a really good language as part of your stack works as a filter-- you get the best programmers that way. Agreed. At one point I felt this way about Scala, but it's starting to change as the boulder rolls downhill. I still use Scala, because it's fantastic, but it's no longer a safe assumption that a Scala programmer can be trusted with sharp objects from the jump.
- voidlogic 12y ago
  >It's not a more popular or established language, yet. Github would disagree as one data point. I don't have my own numbers to back this up but I firmly believe based on my communication that there are more people in the world that have written Go right now than Erlang. >Having a really good language as part of your stack works as a filter-- I think this is good for Go and Erlang... So I don't think it helps distinguish. Not to mention anyone that smart knows C/C++/C#/Java can very quickly become a gopher if needed; quicker I would contend than you will ramp them up on Erlang. >Most interesting to me is your perception of the situation I've been writing Go full-time since before Go 1.0 RC-- I think you don't have an accurate perception of where Go is at.

> I don't really see a compelling reason to switch to it from Elixir/Erlang. What about ease of growing your team and finding 3rd party libraries so you don't have to re-invent the wheel?

MCRed 12y ago

I think it's funny, but not surprising, that you assume it will be easier to grow the team with Go. It's not a more popular or established language, yet. But also, I've recently built a team using Elixir before Elixir was even 1.0. About the hardest possible example of that argument and we found great people, grew a great team in Austin Texas. Having a really good language as part of your stack works as a filter-- you get the best programmers that way. Not saying go is bad, but it's popular, and so you're going to get a lot of people who chose it because it was popular. As for re-inventing the wheel, erlang has a lot of 3rd party libraries, and is ahead of go in that regard, for the time being. Most interesting to me is your perception of the situation, which I'm guessing is driven by the fact that go is very popularly being evangelized right now.

eropple 12y ago
> Having a really good language as part of your stack works as a filter-- you get the best programmers that way. Agreed. At one point I felt this way about Scala, but it's starting to change as the boulder rolls downhill. I still use Scala, because it's fantastic, but it's no longer a safe assumption that a Scala programmer can be trusted with sharp objects from the jump.
voidlogic 12y ago
>It's not a more popular or established language, yet. Github would disagree as one data point. I don't have my own numbers to back this up but I firmly believe based on my communication that there are more people in the world that have written Go right now than Erlang. >Having a really good language as part of your stack works as a filter-- I think this is good for Go and Erlang... So I don't think it helps distinguish. Not to mention anyone that smart knows C/C++/C#/Java can very quickly become a gopher if needed; quicker I would contend than you will ramp them up on Erlang. >Most interesting to me is your perception of the situation I've been writing Go full-time since before Go 1.0 RC-- I think you don't have an accurate perception of where Go is at.