incision

It addresses it as a human being discussing the meaning of the article as opposed to a pedant-bot dicing words to 'win'.

I can't disagree with a single thing said here.

I tend to think of WoW as the Buy-N-Large generation ship of gaming.

It created an entire word that was in some sense a paradise, but at the exclusion of all the awesome, frustrating, exciting, tedious richness that came before it.

Though I have no real idea what I'm talking about...

This feels intuitive to my mental picture of the universe.

The description of this large scale structure and the expansion of the universe has always put me in mind of watching the patterns form and reform from drips in a soapy sink or an elastic fabric being pulled apart.

In both cases, you end up with these big expanses bordered by dense stringy areas. That the motion of the stuff that snaps / shears / collapses or whatever into these strings and knots would be aligned seems perfectly logical.

Not exactly, as the thread you link points out you can reference an image ID in FROM rather than the name:tag which has potential to change silently.

It's the equivalent of using a package manager against a repo you don't own without pinning - expect problems.

This can be mitigated by FROM'ing via ID or avoided entirely by running your registry where tags are reliable.

Admittedly, these things are not necessarily obvious, but I think it's a bit disingenuous to paint Dockerfiles as worthless or broken.

That said, ShutIt looks very cool and seems to address exactly some of my concerns / desires about working with Docker.

I just don't agree with framing it in opposition to and at the expense of what exists.

There's value in a container description that is fully self-contained, transferable and 'dumb' enough to be transparent.

Absolutely.

Thankfully, the Docker team seems in agreement with this based statements about avoiding making Dockerfiles "too clever" and the response to various proposals.

As you point out, most of the "issues" here are really misconceptions.

I expect it's a tough balance for any new(er) project. Maximizing exposure and adoption, but avoiding negative perceptions from being applied in ways aren't optimal.

I expect this sort of thing is hard for lots of people - those without kids - to empathize with. I doubt I spent much time thinking about such things prior to having a child.

Now though, it has become really clear to me how common stereotypes about gender, race and the like are among things aimed at children.

It's not that this one book is going to ruin someone or that any of the silliness it presents is so awful or dangerous.

It's that those ideas are pervasive, that even if you're filtering what you provide directly to your kids they're still indirectly affected by it - an ever present cloud of nudges and judgments about everything from choice of colors, toys, aspirations and even now how to use computer.

It's ridiculous and wasteful.

My guess/hope...

This is aiming to be GMail + Google Now for the enterprise. Something that will parse your mail, schedule and contacts to generate suggestions or reminders and create an easily accessible "context" for each.

A workplace client that can generate 'cards', reminders and contextualize common bits of information (Think UPS tracking numbers in GMail - applied to support tickets, physical sites, projects, POs and budgets in an enterprise) with the creepy accuracy of Google Now would actually be interesting - yet another take on unified communications or a skin deep re-imagining of email would not.