Golang rewrite?

[drmorr0]

Currently, the three main/most complicated components are all written in Rust (sk-tracer, sk-ctrl, and sk-driver). Would like to gauge community interest to see how much of a hindrance to adoption this is. Should some or all of these components be re-written in Golang? There's no particular performance reason why these need to be in Rust, but it's been a good learning opportunity for me. The Rust Kubernetes libraries (kube-rs, k8s-openapi) are both pretty comparable to the Golang equivalents, so I think it would be a decently straightforward port over.

However, I'm just one dev with very limited time, so I'm unlikely to prioritize this over "making new improvements" unless there is significant concerns to adoption given the partial Rust codebase. I'm happy to provide guidance to someone else on this task if they want to pick it up and it's important, though!

[drmorr0]

The converse question is, "should I just rewrite skctl in Rust?" After I finish ripping out sk-vnode and sk-cloudprov (#70), the CLI is going to be the only tool in here written in Golang (and it's very small), and supporting two different toolchains in this repo has been a headache. It would be great if I could just use one language or the other.