4 ms·

Exactly. I am kind of wondering why this 1:1 translation came up why not just follow best practices and implement a functionality instead...

• jessaustin 12y ago
  The path they chose was much more predictable than your suggestion. I.e., after their team spent three days at it, their estimate for the total translation was probably within 50% of the month it actually took them. I don't expect they could have been as accurate in estimating an entirely new implementation.
  • jtolds 12y ago
    Right on. We immediately had not totally horrible estimates for how long it would take. Further, we have always really been inspired by Joel Spolsky's article on rewrites: http://www.joelonsoftware.com/articles/fog0000000069.html http://www.joelonsoftware.com/articles/fog0000000069.html In fact, I can't help but wonder if we would have attempted a Go rewrite sooner if not for that article.
• jerf 12y ago
  I've got a project I'm porting out of Erlang to Go. It's not a transliteration, since it can't be, but by design it's a drop in replacement, modulo a smidge of configuration for each (dozen lines of config, tops). As much as I'd like to GO WILD AND FIX ALL THE THINGS!, it's advantageous to be able to switch back and forth freely during QA and early deployment, because you need a smooth transition.
  • leccine 12y ago
    Out of curiosity what is you motivation for porting something from Erlang to Go?