While I'm both fluent in Rust, Golang and C#, I just don't think Golang is a good choice for Kubernetes operator, the code is simply too terse and verbose, and I can't enjoy a lot of good things such as DI and IoC in Golang, where I think C#/Kotlin's approach by using primary constructor is very intuitive for me, and it is really a game changer for the coding mindset, especially when you have LLM, without DI there will be a lot of spagetti code entanglement. I use DI to facilitate functional separation and modularization of code.
It is not like I don't know that Golang's interface could do that. It's just C# simply did better. I do enjoy using Golang for writing network application such as network protocols and IO intensive workload, which is where Golang really shine through Goroutines, but if you want a generalist that is famiilar and did all-rounds, I would still consider C#/Java/Kotlin for that purpose.
I have so many questions! Why did you decide to use C# instead of Go? How does the C# Operator SDK compare to the Operator SDK or Kubebuilder?
While I'm both fluent in Rust, Golang and C#, I just don't think Golang is a good choice for Kubernetes operator, the code is simply too terse and verbose, and I can't enjoy a lot of good things such as DI and IoC in Golang, where I think C#/Kotlin's approach by using primary constructor is very intuitive for me, and it is really a game changer for the coding mindset, especially when you have LLM, without DI there will be a lot of spagetti code entanglement. I use DI to facilitate functional separation and modularization of code.
It is not like I don't know that Golang's interface could do that. It's just C# simply did better. I do enjoy using Golang for writing network application such as network protocols and IO intensive workload, which is where Golang really shine through Goroutines, but if you want a generalist that is famiilar and did all-rounds, I would still consider C#/Java/Kotlin for that purpose.