> The UI is clunky. The UI was originally designed with one end in mind: "Show me what is broken and take me there as fast as possible". I and others have giv

> The UI is clunky. The UI was originally designed with one end in mind: "Show me what is broken and take me there as fast as possible". I and others have given lots of feedback about the strengths and limitations of that orientation, particularly trading off between a job-oriented and resource-version-oriented view of the world. > There are simple scenarios like deployment rollbacks who are hard to do. I've had this with the CF resource. The Concourse-y solution would be an undeploy resource. > For some reason they decided to develop their own container engine which leads to all sorts of trouble and maintenance issue. The container engine is garden-runc, the actual containerising is the same code as Docker's. What I like a lot less is container orchestration. I have complained about this in a ha-ha-only-serious matter. Disclosure: I work at Pivotal.