I have no affiliation with Engadget (in fact, I've spent over a decade working at competitors to Engadget). But I've found that it makes sense to evaluate news organizations' output on an article-by-article basis. Even the best news organizations can screw things up on occasion, and even excellent reporters can be assigned derivative stories by their editors.
The article-by-article approach is what http://recent.io/ uses in its pipeline, which is working very well in testing so far.
More to the point, this looks like a perfectly decent story and an engaging read. The writer even managed to avoid being snarky about Samsung trying (sigh) to second-guess John Carmack!
People really need to stop always quoting Joel - he is not a definitive go-to software spokesperson, and has some very strong (and often wrong) opinions about things -- shaped by years at Microsoft doing things only the Microsoft way.
~~
He is puffing his product in this blog post -- nothing more.
He's stating facts about his startup. It's not like he's giving some opinion on something he's not qualified for. It's like saying we shouldn't ask Woz we he made Apple Basic.
Well, Docker just slapped a "1.0" sticker on and called itself "production ready" when it clearly wasn't (features like in this 1.2 release are kind of mandatory for any serious deployments).
Yea, i really thought that this stuff should be out of dockerland. Not that i dislike the feature, just that it seems to overlap with established tools that excel at doing one thing well.
FWIW, now that docker is handling the restart/monitoring it can actually do it better than if systemd is doing it, since docker knows that it doesn't have to tear down and re-create the network namespace, unmount/remount the container's FS, etc.
So when a container is restarted via the restart policy, it not only happens faster, it will get the same IP as well.
