[altcognito]

> I have been concerned that Docker's scope was expanding too far for a while now

What features were recently introduced that it increased Docker's scope?

[lclarkmichalek]

Talk of Docker cluster, which might include a network overlay layer a la weave

[shykes]

All of which will be fully pluggable with a "batteries included but removable" design, just like we did with sandboxing and storage.

[lclarkmichalek]

You may need to make that clearer to some of the people that are due to be building your plugins: reading http://weaveblog.com/2014/11/13/life-and-docker-networking/, I get the feeling that they're not thrilled about it.

[shykes]

maybe they're busy designing the interface and implementing a proof-of-concept with us as we speak, instead of blogging and twittering.

[lclarkmichalek]

Welp, I'm putting "been snarked by founder of Docker" on my CV.

[shykes]

I guess so - sorry ;)

I hope you can understand that it's frustrating when, after hard work pitching an API to dozens of ecosystem players, spending weeks trying to wrangle a working implementation which makes as many of them as happy as possible, without compromising integrity of design - after all that, in the end, all it takes is one unhappy camper to write a blog post and that immediately tramples everything else.

It's even more discouraging in this particular case, because after this blog post, Alexis and I have discussed this topic extensively, and as a result he has since joined the effort. In fact I will be hacking with him in person on integrating Weave as a native networking plugin in 2 days in Amsterdam.

So, sorry for the insta-snark. But it can be frustrating to see so much good will and hard work be crushed in a second.