I believe it's high time to update the our website with some new copy (what we have presently hasn't been updated for a while), and I wanted to reach out to you for feedback in the hopes of making some improvements before MesosCon (and my talk!).
While I've always felt the most apt description for Mesos was as a "kernel" in order to emphasize the power of the primitives for building new distributed systems, in the earliest days I tended on the conservative side with my choice of language as I felt it was easier for folks to grasp Mesos. But I feel like our project is at a level of maturity where that is less of a concern, and my gut is that we should really embrace the kernel messaging in order to leave folks with the right first impressions about the technology, especially with respect to what it facilitates today and what we hope it will facilitate tomorrow. I've pasted some new copy below that I'd love feedback on. We haven't really done much of a review process for the website in the past, but I thought I'd share this more widely in order to get any feedback before making any updates. Looking forward to seeing many of you at MesosCon this week! ------------------------------------------------------------------------------------------------ Headline: Program against your datacenter like it’s a single pool of resources. Subhead: Apache Mesos abstracts CPU, memory, storage, and other compute resources away from machines (physical or virtual), enabling fault-tolerant and elastic distributed systems to easily be built and run effectively. Distributed Systems Kernel Mesos is a distributed systems kernel built using the same principles as the Linux kernel, only at a different level of abstraction. The Mesos kernel runs on every machine and provides applications (e.g., Hadoop, Spark, Kafka, Elastic Search) with API’s for resource management and scheduling across entire datacenter and cloud environments.
