> but DC/OS has yet to demonstrate that it can do any of that [...] its the other 29 things that's going to fail at scale.
Of course you are right that in DC/OS there is a lot more besides Mesos that could fail at scale. That is why we are carefully scale-testing DC/OS in its entirety -- under lab conditions (internally) as well as under real-world conditions (large production environments). We will be more transparent about this in the future, but one example I can give is that we regularly run DC/OS on 10^3 nodes for testing purposes.
> if you are going to be running DC/OS at that scale, then you are going to be running the enterprise version
I am not convinced by that argument. Still, just to clarify, Mesosphere Enterprise DC/OS does not have better scaling characteristics than (open) DC/OS. We are trying to land all corresponding goodness in DC/OS.
> killing non-DC/OS mesos/marathon
I understand that brutal decisions have been made. But if you look at Mesos and Marathon as of today (btw., there is no such thing as "non-DC/OS mesos/marathon"), progress is being made at an impressive rate. I observe more "animating" than "killing".
> while crippling non-enterprise DC/OS
I only see additions, no removals. Also, if you were looking at the core technology stack, the delta between Enterprise DC/OS and DC/OS will probably appear to be surprisingly small to you.
> The "K8s doesn't scale" argument is losing ground with every new release btw.
I agree.
The "scale argument" is insignificant compared to other aspects in most of the cases anyway. As we all know :-).