On Kubernetes, Docker, and lowering the barrier to entry

Andy Clemenko: Any time there's a new technology, developers have to lower the barrier to entry, especially for changing. For changing abstraction views and for changing tooling, you've got to make it easy. Rancher did a fantastic job of making orchestration easy. They had to catalog, and my God, it was great.

I had a company director once who wasn't a computer geek at all. To be able to deploy a ghost blog server by clicking two buttons blew his mind. You just have to make that barrier to entry really low. The problem I see with Kubernetes right now is that the YAML in itself uses spec four times in a single object type. YAML format is fine, and everyone can do the vertical lines and, in their code, get the spacing right.

But its overall structure? Well, a customer yesterday was talking about Swarm versus Kubernetes, and how you can take a single object in Swarm, and it describes the ingress URL-FQDN, it...