I understand. But from the point of view of Deis, CoreOS is not a platform. It is a Linux distro with a loose collection of tools pre-installed, some of which Deis happens to use. One such tool is Fleet. Another is the systemd log journal. Each of those tools has dozens of competitors. Deis reserves the right to pick and choose from those competitors without locking themselves in. It also reserves the right to use some pieces of CoreOS without using the other. If you think of CoreOS as an end-to-end monolithic platform, this may seem strange. But it is perfectly aligned with the Docker philosophy, which is that big monolithic platforms are not a good thing. What you want is a vast ecosystem of small composable lego bricks.

> Deis reserves the right to pick and choose from those competitors without locking themselves in.

Well of course! It is your own project.

> If you think of CoreOS as an end-to-end monolithic platform, this may seem strange.

Yeah, but I'm not looking at CoreOS as an end-to-end monolithic platform. I'm looking at it as a bunch of components that happen to be bundled together, each of which is pretty nice all by itself. It doesn't mean you have to use them all, but on the other hand, you would hope that if you were going to replace one of them entirely you'd go with something with a significant advantage (and I'd argue in some cases it has gone the opposite way).

> What you want is a vast ecosystem of small composable lego bricks.

Understood. I just don't think you help yourself much if you take out one brick and replace it with one of your own, particularly if the new brick isn't any better than the old one (and might be worse).

I should clarify that I am not part of the Deis project, although I know Gabriel and follow their roadmap closely.. Sorry if I wasn't clear.