3 ms·
From description: "In this talk we explore the devastating effects using object oriented antipatterns in go while building programs in a monorepo. ... Unknown
by 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 agoThis 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.