4 ms·

I'm a huge fan of Go, but moving from Ruby to Go can't be a decision based on performance gains only. There are a lot of advantages the Ruby language and ecosy

by iagooar 12y ago

I'm a huge fan of Go, but moving from Ruby to Go can't be a decision based on performance gains only. There are a lot of advantages the Ruby language and ecosystem provide. What about programmer happiness and productivity? What about the experienced Ruby devs you surely have? Are they wanting to switch to Go? What about the lack of experience using Go? Are you sure you're going to avoid all the pitfalls of the new and shiny language? Isn't better hardware cheaper than your devs' time? I'm not saying that your decision is wrong, and probably you have put a lot of thought into it, but most of time, developing software is using tools you know well, that are battle hardened and have been proven to deliver fast.

ChikkaChiChi 12y ago
If a performance gain improves the user experience by either making your product faster or by expanding the ceiling in which you can introduce new features, then yes, the decision can be based on that metric only. I can appreciate many of the points you made, but programmers are happiest when they can eat, and happy paying customers can put food on the table :)
curun1r 12y ago
When the performance you're considering is your own machines, I wholeheartedly agree with you. But when the performance you're considering is that of your customers, the story changes. The guys who wrote the story are building a monitoring product and their agent code will be installed on all of their customers' machines. Every CPU cycle and byte of RAM should be sacred to them because it takes those resources from their customers' applications.