Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In 2016 I would write networking and RPC in go.


"networking and rpc" must be written in the languages your server and client are written in, (or something compatible).

Writing a networking library in Go does nothing for Facebook if their services are written in C++.


Because you want to spend 10x as many CPUs?


Mostly because it's easier, performant, and because of the nature of the language it's less likely I would make a mistake doing anything in the language compared to C++ or C.


Me too - and I don't even know C++.


I was joking that the main reason for dismissing C++ for this task so quickly was not knowing it, and when and where C++ is used.

How did I came through, to be so unvoted? I'm confused.


[flagged]


Articulating concerns with Go is a legitimate (if, for this particular thread, unproductive) way to use HN. Writing comments like "Go is a toxic language" is not; it's morally indistinguishable from trolling.

The comment rooting this thread, suggesting the use of Go instead of C++, was also unproductive. I'm glad to be done with the C++ part of my career, but still happy to read about ambitious new libraries built in it. That upthread Go comment is the kind of tangent-driving chaff that made Slashdot unreadable. But this comment is even worse.


Point taken. Made comment less polarizing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: