Why Go and Not Rust?

Re:Why Go and Not Rust? by elsurudo on Monday September 16, 2019 @10:54AM (#20984657)

I assume the GP meant "scale of codebase complexity" – which is orthogonal to whether something is "web scale" (ie. everything Google does).

[ Parent | on HN ]

Re:Why Go and Not Rust? by creyes on Monday September 16, 2019 @11:02AM (#20984747)

Isn't the Google codebase infamously a monorepo with billions of loc? That seems like it fits "scale of codebase complexity" as well as "web scale"

[ Parent | on HN ]

Re:Why Go and Not Rust? by munificent on Monday September 16, 2019 @01:07PM (#20986185)

It's a monolithic repo, but not a monolithic codebase. It contains many many separate projects, libraries, and applications. There's a lot of code reuse, but it's not like you have to wrap your head around the whole thing.

[ Parent | on HN ]

Re:Why Go and Not Rust? by jcranmer on Monday September 16, 2019 @11:05AM (#20984784)

Yes, but much (if not most) of that codebase is in C++.

[ Parent | on HN ]

Re:Why Go and Not Rust? by jimbokun on Monday September 16, 2019 @07:08PM (#20989461)

How do you check out a project like that?

[ Parent | on HN ]