If it were just an open source project, it could focus on nothing, because Solomon would be working on something else that would actually pay his bills.
It's just a young project with a huge interaction surface, they're trying to please a lot of people in a very small amount of time. No reason to panic, just wait for it to get finished.
Also, Docker is an extracted product just like Rails is, and it's not really a framework so I don't think DHH's argument really applies here.
1. Write code to verify signatures.
2. Write code to print "The image you are pulling has been verified."
That's wild speculation, and the elephant in the room (Linux), while a different beast, is a pretty strong counterexample for how being 'just' open source oesn't doom you to being slow or insecure.
> It's crazy to assume that if it were an open source project it would somehow get the core right faster or not expand on its ambitions.
I don't think it's crazy at all. A (say, community funded) purely open source project has no distractions and has nothing to do but to get the core right. It also has no incentive or reason to expand its ambitions.
I can give you a couple of counter-counter-examples.
GIMP has been around for almost 20 years by now, but its development rate is abysmally slow, still faraway from what most people expect from a Photoshop replacement. Its progress since ~2008 hasn't been that big.
GNOME has been around for almost that long too, but it's constantly suffering from lack of man power.
The Sidekiq background worker system for Ruby is open source, but development went much faster ever since the author started monetizing on it by selling commercial licenses.
Nginx is also open source. They have much more development power now that they are a business and have a source of income. Before, it was just Igor working on it whenever he had time when he's off work.
with a nod towards systemd.
Funny, systemd-nspawn just gained the ability to import and run Docker images. Or rather "the best known container solution".
In particular, I don't believe dotCloud ever ran Docker in production / for paying customers. It seems like there were several earlier containerization technologies based on LXC or OpenVZ, but it wasn't Docker per se. They had some domain knowledge from those earlier experiences, but not production quality code.
The core managed at the Org will have less marketing bubble-words, lies and hype, so we keep trusting their goals and mission, while the corp can do whatever they want to achieve their distinct goals.
Seems to me that they'll either license tech to enable enterprises to build their own docker platforms, or offer their own hosted platform... dotcloud 2.0
“The closest analogy I guess I can give you is, for people who think of Docker and containers as a new form of virtualization, so [with] open source we gave away ESX and what we are selling is something akin to vCenter or vSphere.”
This also clarifies why things like Rocket are the biggest existential threat facing Docker Inc., and why the mud is being slung.
On everything else I'm on the fence but so far the 'batteries included, but swappable' motto has been respected: everything new they have done/announced lately is not in Docker core but rather an external project (think: Swarm, Machine, Compose) that uses the public APIs
All the new features are pure open design, they only exist because users are asking for them and people are sending patches.
If Docker was just an open source project, it could focus on getting the core tech right. But Docker is also a startup, and the startup can't stay differentiated unless they keep adding bells & whistles, all of which stay tightly integrated.
See also "Why there is no Rails Inc" (http://david.heinemeierhansson.com/posts/6-why-theres-no-rai...)