Hacker News new | ask | show | jobs
by bobofettfett 4129 days ago
If you move from Ruby to Go and this works better for you, then choosing Ruby in the first place might - if it was not about a prototype or getting VC money or only found Ruby developers - be a failure on your part.
1 comments

Ruby got them customers within the bounds of their time and money budget so it did its job. Nothing in the post suggests they have regrets about it but it would be interesting to hear from them.
Without Ruby we couldn't have build lots of features with such a tiny team. We don't regret and we are not replacing Ruby entirely (just few parts)

85% of our server codebase is still Ruby.

When Ruby can't solve your business problems -> wrong choice. If it can solve your business problems -> wrong choice to move to Go.
Yes, couldn't read find that in the article beside "monolitic baeh"
Requirements change.