12 ms·

So, in nutshell: Build your web apps in something hyper productive like rails to proof of concept them, then find the high load bits and replace them with a go

So, in nutshell: Build your web apps in something hyper productive like rails to proof of concept them, then find the high load bits and replace them with a go service. Seems like reasonable, if generic advice: prototype quickly, then go back and rebuild in something performant if its successful. Iterate quickly, etc. etc.

jandy 14y ago
This has been the practice in Ruby for quite a long time (albeit without Go). Usually high load/slow areas are rewritten as a C module. So yeah, sound advice but nothing revolutionary. Go looks nice though.