marathon

What's hard is stopping the next Boston marathon bomber without doing more damage to our country than the next Boston marathon bomber would do.

I'd say that 1/26th of the effort of running a marathon is taking the first step, never mind the first mile.

On a hot day, the two scientists wrote, a human could even outrun a horse in a 26.2-mile marathon.

You'll need to tag those instances as they're launching so Marathon will know they're public/private respectively.

At most, they shifted from organized plots (like that of 9/11) to less-organized events (like that of the Boston Marathon bombing).

And that's hard, because despite the loss of life, the Boston Marathon bomber didn't actually do much damage to our country.

But if you're doing a 3h whiteboard marathon or work from your own chair?

What's hard to answer is how do you stop the next Boston marathon bomber.

This reminds me somewhat of reddit's DIY investigation into the Boston marathon bombings.

Not only how do you stop the next Boston marathon bomber—that's relatively simple.

The likes of Mesos, the Mesosphere ecosystem with Marathon and Chronos, and Docker Swarm bring only the primitive parts of the whole picture.

The 1980s and 1990s changed that and the Dotcom Boom made the Startups and marathon coding that required more time per week to work.

I did this "the long way" over the last 8 years taking it as a marathon more than a sprint.

Marathon is a generic end-user framework for accessing those functions and runs on top of Mesos.

Then Marathon/Aurora/Hadoop/etc tells Mesos to farm out compute jobs to these end client nodes (aka schedules).

Thereby giving you a more opinionated layout for your compute cluster, while running other peer Mesos services, such as Hadoop, Chronos And Marathon.