|
|
|
|
|
by commentzorro
3506 days ago
|
|
> I bet that if an experienced Node.js developer rewrote the entire service again in Node, you would also get 2x speedup. Maybe, but why not try Go on a small piece and see how it works. > I can't believe the CTO of digg bought this... You make it seem like the CTO was somehow being conned. Like Go was a bad choice. Maybe it was as simple as wanting to see what another language offered and this was a good time to try it out. > Why can't developers just admit that they don't know how to scale a service?! It's not the language that's the problem, it's you; it's always you! Oddly enough, this is a language feature built into Go from the get-Go. The language is designed such that a mid level programmer can ramp up and write performant Go code in a short amount of time without needing years (or even months) of experience, theory, classes, third party libraries, tooling, etc. It's a bold experiment and it may not succeed. Has it for Digg? |
|