Solomon, in case it's not clear why people are upset, I'll spell it out:
1) You're lashing out at the very community that supports you. Instead of listening, seeing problems, and changing, you constantly dump the blame on your users and partners for the sake of your ego. If there's a communication problem you need to realize it's your fault and your responsibility to remedy it. Your users aren't being paid millions to make Docker work. You are.
2) This spec is clearly half-assed and intended to shut people up, not actually move anything forward. You and I know that nobody is going to do anything with this spec, because there's no reason to think it won't be broken by a change in Docker core tomorrow.
I don't even think a spec is necessary here: what Docker needs is options. By which, I mean Docker needs to be sliced up into small enough, simple enough pieces that you don't need some huge slapped-together ad-hoc spec to take Docker apart and adapt the guts to your needs.
This isn't an open specification, this is a bible from the Docker gods dictating the container commandments, which are subject to change when Zeus gets pissed. Please know the difference. Worse, at the end of the "spec" is an apology of its existence, making it clear that the intention isn't to listen to people but to tell them how it is.
3) I know this puts Docker in a tough place as a business, but everyone's getting the impression you're forsaking the early adopters and hackers that got Docker off the ground in the first place. This is somewhat ironic: you reminisce about the good ol' days of HN when it was about hackers building things, when it seems the company's goals have shifted away from actually building things to shutting up the proles and supporting enterprise interests like locking everything down and keeping things stable because big bucks are paying to keep it that way. If that's where Docker wants to go, your perogative, but I don't know why you're surprised that the grassroots hackers you're abandoning are turning on you.