Earlier quoted context omitted.
>turned down by Apple and Google It was Google. Because he didn't know what a binary tree was or something similar during the infamous Whiteboard test. But I mean it make perfect sense. Google is all about building AI, ML, Algorithm, K8S etc. Complexity is their KPI, usefulness is not. So may be it isn't so much a bad thing after all. He wouldn't have fit in. Edit: I guess the tone didn't shine through. The "all abou…
It also made sense that they'd make an absolute dogs dinner of golang package management after turning him down. Some things are not in google's DNA.
I think this reasoning explains a lot of my frustrations with Go: it's Google's language that they kindly let you use, it didn't grow organically within many communities and companies across a whole range of use cases and codebase sizes.
You have a similar thing with git, it was the kernel's VCS that you could also use if you wanted, but especially early on it was rather hostile if you didn't actually need to maintain a gigabyte-sized monorepo with hundreds of third-party contributors mailing patches to various subsystem maintainers that would then have their branches merged into the mainline. Fortunately git's usability has improved a lot since then.