3 ms·

> If you're building web backends, Rust is not a good choice This heuristic wouldn't work for my department because we build web backends in C++. I keep tellin

> If you're building web backends, Rust is not a good choice This heuristic wouldn't work for my department because we build web backends in C++. I keep telling the most senior devs here that nobody does this and for good reasons (velocity etc), and their response is "who cares what the rest of the world does, they're just bad at C++."

Animats 4y ago
Google developed Go specifically so they didn't have to use C++ in high-volume web backends, which is what they did previously.
- hot_gril 4y ago
  These aren't high-volume, they're just web interfaces used internally by hundreds of people. Golang wasn't well-received either in our dept. Java would've saved us a lot of headache, a phrase I never thought I'd say; adjacent teams use it for similar things.
- Frog0fWar 4y ago
  Another (maybe even more) important motivation was to have simple, statically-typed language so that new hires can contribute to the codebase faster and the code itself is more standardized and easier to maintain at large scale.
  - hot_gril 4y ago
    They basically got there with Java + some frameworks. It's not the best (I'd like NodeJS), but it works and has a huge ecosystem already, and anyone can use it. Some people complain that Golang is designed specifically for its original use case of specialized web backends and isn't great otherwise, or that its main design goal was being "not C++."
- pcwalton 4y ago
  Google absolutely uses lots of C++ in high-volume web backends today. Go didn't replace it.
- za3faran 4y ago
  A few people at Google did, as far as I'm aware it didn't start as some officially sanctioned project at the company. golang has its own sets of challenges due to the limitations of the language and its error prone bare bones threading model.
- pjmlp 4y ago
  Nope, Google is fine with Java and C++. Go authors always disliked C++, and got a manager that allowed them to work on their toy language, which eventually became Go.

Animats 4y ago

Google developed Go specifically so they didn't have to use C++ in high-volume web backends, which is what they did previously.

hot_gril 4y ago
These aren't high-volume, they're just web interfaces used internally by hundreds of people. Golang wasn't well-received either in our dept. Java would've saved us a lot of headache, a phrase I never thought I'd say; adjacent teams use it for similar things.
Frog0fWar 4y ago
Another (maybe even more) important motivation was to have simple, statically-typed language so that new hires can contribute to the codebase faster and the code itself is more standardized and easier to maintain at large scale.
- hot_gril 4y ago
  They basically got there with Java + some frameworks. It's not the best (I'd like NodeJS), but it works and has a huge ecosystem already, and anyone can use it. Some people complain that Golang is designed specifically for its original use case of specialized web backends and isn't great otherwise, or that its main design goal was being "not C++."
pcwalton 4y ago
Google absolutely uses lots of C++ in high-volume web backends today. Go didn't replace it.
za3faran 4y ago
A few people at Google did, as far as I'm aware it didn't start as some officially sanctioned project at the company. golang has its own sets of challenges due to the limitations of the language and its error prone bare bones threading model.
pjmlp 4y ago
Nope, Google is fine with Java and C++. Go authors always disliked C++, and got a manager that allowed them to work on their toy language, which eventually became Go.