EthanJJackson

"It’s a no brainer that the search engine giant will be compelled to bring a similar anti-ad tracking feature on Android to keep the mobile ecosystem in sync."

Huh? Perhaps I'm missing something, why would Google do the same? Seems out of their interests ...

Completely agree. In case it's helpful, we're working on a cloud dev environment for Docker that addresses the resource issues by running containers in the cloud instead of locally: http://kelda.io/blimp

Of course, if you can avoid docker for local development, that's definitely easiest in many cases.

I agree. I would never put data in a container in production, but for development purposes it can be helpful.

FWIW I think they definitely have a place going forward. But also don’t think the hype is helpful. It’s a big complicated change with goods and bads. Folks should know what they’re getting into.

Ethan J. Jackson here, Founder/CEO of Kelda, and author of the post.

Thanks for the comment! You are, of course, right, once the initial OCR standard was developed, it acts as sort of a thin-waist under which tons of innovation in container runtimes are possible.

The main goal of the post was to provide a high-level overview for folks new to containers that need a beginning working model on what this stuff is all about. So I elected to omit this (and other) details in the hopes of being a bit easier to grok. But I think you’re right, I could definitely have clarified the point a bit more.

Already in progress =)

I'm working on an approachable (i.e. easy to setup and manage) container orchestrator at http://quilt.io that may be worth checking out. It's still very early beta quality software, and some features are missing (notably bare-metal isn't there yet, but it's on the roadmap). That said, it's designed to solve precisely this problem -- ops shouldn't be this hard.