Go vs. Rust: Writing a CLI Tool

Re:Go vs. Rust: Writing a CLI Tool by harpratap on Tuesday August 04, 2020 @08:44AM (#24049342)

> The Go code in K8s is simple, the system of Kubernetes is complex

Can you link me to a doc which explains the runtime scheme type system of Kubernetes? Could never wrap my head around how that even works. And why they had to even do this in the first place?

[ Parent | on HN ]

Re:Go vs. Rust: Writing a CLI Tool by yahyaheee on Tuesday August 04, 2020 @09:50AM (#24049913)

This is the best I can find https://kubernetes.io/docs/reference/using-api/api-concepts/ there used to be a better doc on this but I can't seem to find it again.

Runtime scheme and the k8s machinery can be pretty awkward. Scheme is just a way of registering the available datatypes by group/version/kind so the client can look at any given object and figure out if it knows how to decode it.

[ Parent | on HN ]

Re:Go vs. Rust: Writing a CLI Tool by harpratap on Wednesday August 05, 2020 @02:02AM (#24057708)

This doesn't explain it at all, specially the ecosystem surrounding schemes - informers, cache clients and various other code generators for typed as well dynamic API clients

[ Parent | on HN ]

Re:Go vs. Rust: Writing a CLI Tool by majewsky on Tuesday August 04, 2020 @09:43AM (#24049851)

> why they had to even do this in the first place?

Because they wanted stuff like Watcher<T>, but Go does not have generics.

[ Parent | on HN ]