4 ms·

Or it may be because Java and C++ are much older so lot more code is written in those. And companies do not replace working code just because new language devel

by geodel 7y ago

Or it may be because Java and C++ are much older so lot more code is written in those. And companies do not replace working code just because new language developed in house has few more features.

pjmlp 7y ago
Except that lots of new code also get written in those languages. Google's major Go projects appear to be gVisor, Android GPGPU debugger, Fucshia's TCP/IP stack and volume management tools and the download server as it was done by the Go team. https://commandcenter.blogspot.com/2012/06/less-is-exponentially-more.html https://commandcenter.blogspot.com/2012/06/less-is-exponenti...
- xxxpupugo 7y ago
  You forgot kubernetes
  - pjmlp 7y ago
    I did indeed. https://archive.fosdem.org/2019/schedule/event/kubernetesclusterfuck/ https://archive.fosdem.org/2019/schedule/event/kubernetesclu...
    - geodel 7y ago
      From description: "In this talk we explore the devastating effects using object oriented antipatterns in go while building programs in a monorepo. ... Unknown to most, Kubernetes was originally written in Java. If you have ever looked at the source code, or vendored a library you probably have already noticed a fair amount of factory patterns and singletons littered throughout the code base. " So basically writing Java in Go lead to clusterfuck codebase.
      - smarterclayton 7y ago
        This is a joke talk (hyperbolic) Most of the codebase problems in Kube are: 1. we depended on half the Go ecosystem at one point (docker, grpc, etcd, a few others) which is hard to do with dependencies in go (few standardized libraries) 2. performance of serialization mattered and JSON and protobuf were still raw at the time I don't think Kubernetes is any worse than any other large (3M+ LOC), relatively young codebase I've seen on average.