> Don't all these steps seem like a lot of disk, cpu and system-dependency-intense operations just to run an application? I'm not sure I follow. At least compa

> Don't all these steps seem like a lot of disk, cpu and system-dependency-intense operations just to run an application? I'm not sure I follow. At least compared to using Docker it doesn't seem much different at all in terms of overhead. > Why is this thing written in Go when a shell script could do the same thing while being more portable and easier to hack on? Go runs on more platforms than Linux containers, so I don't think Go is going to be a limiting factor. If you think shell script programming is going to lead to more robust and efficient software... ;-) > Why are they saying this thing is composable when they just keep shoving features (like compilation, bootstrapping, configuration management, deployment, service autodiscovery, etc) into a single tool? They aren't a single tool? They've architected it so that those different components are quite separable, particularly the ACI is really, really separable from the rest.