5 ms·

The Kubernetes codebase would probably be a lot less complicated, if Go the language itself were not so simple: https://medium.com/@arschles/go-experience-repor

• ex_amazon_sde 7y ago
  If anything, Kubernetes is a good example of where Go should not be used.
  • pjmlp 7y ago
    They were going to use Java, but it was deemed too complex and there was strong pro-Go advocacy to move the prototype away from Java into Go. https://changelog.com/gotime/105 https://changelog.com/gotime/105 https://archive.fosdem.org/2019/schedule/event/kubernetesclusterfuck/ https://archive.fosdem.org/2019/schedule/event/kubernetesclu...
    • aganame 7y ago
      Kubernetes beat Mesos/Marathon, which is written on Scala. I don't think that's just a coincidence.
      • pjmlp 7y ago
        Failure of a project's adoption usually traces back to people and management, not technology.
      • monocasa 7y ago
        I think that has more to do with the fact the k8s devs had a complete implementation of the the same product (Google's Borg) as reference. Mesos/Marathon only had a couple 10 page journal articles to look at and a ton of on the ground decisions to make and quantify the choices of.
  • mroche 7y ago
    I’ve heard the statements that the Go stdlib and Kubernetes are not good examples of Go code, but I’ve never seen someone say that it’s not a good use case for Go. Would you mind elaborating on that assessment?