5 ms·
Part of the issues with Kubernetes is that it started as a Java project and then it became a Go project. If anyone started a large Go project with that mindset
by studmuffin650 6y ago
Part of the issues with Kubernetes is that it started as a Java project and then it became a Go project. If anyone started a large Go project with that mindset it would look messy no matter what you did.
- bad_user 6y agoCan you point to any large Go project that isn’t a mess? I agree that from a single sample you can’t reach conclusions, but “it was their fault” isn’t a great defense.
- nix23 6y agoCan YOU point to any large project that isn’t a mess?
- oDot 6y agoServo
- nix23 6y agoAhh with 3250 open issues and 8k closed ones? With the main-driver being Mozilla?
- nojvek 6y agoIsn’t mess relative to the beholder of the eye. Many large projects may look like a mess but their success is because they got the high level architecture right and perhaps had the moat of a large tech behemoth behind them. VSCode, Tensorflow, Kubernetes, Go, Typescript, React. These are a few that come to mind. At a high level, they are all fantastic projects and perhaps messy in their own way, but they are absolutely fantastic, hardened proven codebases with ~millions of users.
- mehrdadn 6y agoIs rclone a mess? I don't do Go, but some glances at it don't scream "mess". https://github.com/rclone/rclone https://github.com/rclone/rclone
- jtlisi 6y agohttps://github.com/thanos-io/thanos https://github.com/thanos-io/thanos