Almost nothing that you say here is true. I should know. I am good friends with all three of the original authors of Mesos: Andy, Ben, and Matei together. We s

Almost nothing that you say here is true. I should know. I am good friends with all three of the original authors of Mesos: Andy, Ben, and Matei together. We sat next to each other for years while working on our Ph.Ds at Berkeley -- first in the ParLab/RADLab, and then in the AMPLab. As a quick disclaimer I should mention I am now an employee of Mesosphere. I joined Mesosphere because I believe in the technology they are building, and it is certainly not 1-2 years behind everyone else. In fact, I left my job at Google to come here. To touch on the exact points that you make. Andy would agree that Mesos was not purely his own "brainchild". Ben, Matei and Andy all worked on it together as a class project in the Spring of 2009 (I was also in this class, so was able to witness it all first hand). Moreover, many of the ideas in Mesos were largely an extension of some of Ben's previous work on Lithe: a multi-level scheduling framework for managing multiple parallel libraries in a single application. I even took some of Ben's Lithe work and extended it for part of my Ph.D work. If anything, Mesos was the brainchild of Ben more than Andy in this respect. As time progressed, Andy and Matei decided to focus more on Spark than on Mesos itself. This has lead to the (very successful) Databricks startup they created. Ben, on the other hand, decided to focus more on Mesos itself, bringing it to Twitter and now to Mesosphere in order to commercialize it. Andys internship at Google has almost nothing to do with how Mesos has progressed over time. The internship itself was significantly after the initial Mesos paper was published, and focused mostly on evaluating the performance of Omega over Borg. I know this because I saw him give a talk on his work on Omega shortly after completing the internship. To claim that Andy took the ideas from Borg/Omega and applied them directly to Mesos is simply false. To claim that Mesos is somehow stuck in the past is also false. It's true that Google and the AMPLab collaborated closely in the early days with people like John Wilkes and others giving lots of feedback, but Mesos has grown quite a bit since then. They haven't been simply sitting around warming their asses either.