[nowprovision]

I think so. The lack of parametric types leads to an explosion of types for each concept, and where they don't do this a load of casting from runtime.Object and interface{}. The lack of exhaustive pattern matching is responsible for many bugs, oh we forgot to add a case for runtime.InternalEvent etc... However our project will be using Kubenetes library and thus we're also doing it in Go. MetaAccessor another eye sore. It's all a trade-off I guess..