Pretty sure that when you have to wadge a battle against obvious technology to justify your business model, your industry is going to end up on the wrong side of history.

These books are pretty much a must read for anyone interested in the internals of Unix-type systems. I keep them right next to my TCP/IP Illustrated volumes, I reckon it's always good to have good reference material handy - especially when it is well written and researched.

You sold me. I'm not particularly interested in knowing enough about FreeBSD to diagnose anything non-trivial, but I am interested in learning about design decisions behind operating systems.

Trying not to be a curmudgeon - but I really don't see what the big fuss is about, or how docker is fundamentally changing anything.

Not to take anything away from docker being a decent tool in some circumstances - but really this methodology has been around in one implementation for ages on Unix platforms.

That's sorta where I've been coming up, too. Great, hard working group but docker strikes me as a very small component of the deployment stack, the entirety of which doesn't even have much enterprise value.

What would be a good comparison for a component company like this getting to 100s of millions or $1b?

LOL. The massive and obvious enterprise value is in having a standard way to deploy and interface isolated Linux applications along with their dependencies, along with a convenient hub for distributing and exchanging them.

No, its not the first time any technologies with _some_ these types of capabilities have been available, but it is the first time this powerful combination of those capabilities have come together in a way that has so much momentum.

That's fair. And you're absolutely right that the technology has been around for ages.

I would ask - why is it now that it's actually being used outside of the few boutique scenarios that came before?

I personally think it's a change at various levels of the industry (from the speed of ideation->delivery, inefficiency in process, dc consolidation, efficiency/density) and Docker is an integral piece in helping alleviate those problems

Docker is just one piece of the puzzle. They still have a lot of work to do, as he said in his comment. Things like container orchestration, networking, service discovery, etc. If you read the linked blog post, they actually explain this at the end of the article.

+1 from the systems engineer with over a decade experienceat cutting edge facilities - and a BA in philosophy (focused on recent continental thought, not logic). It comes down to the individual and their passion.

Not sure why anyone would surprised about this. It's in the same mentality that allows things like Sean Parker's wedding fiasco in Big Sur happen.

I thought his explanation was pretty good. Why was it unsatisfactory? http://techcrunch.com/2013/06/27/weddings-used-to-be-sacred-...

Well that explanation IMHO is just another argument as to how people in these positions have zero regard for shared spaces and others in general. I reckon the valleywag has a pretty funny response to that self serving article he wrote.

I'm not going to start a bikeshed over the technicalities covered in the coastal commission report though - my original point was how little regard many of these individuals have for others. And how no one should really be surprised that the technology community seems to represent the worst case examples of this.

Considering how clearly Sean Parker's high regard for redwood forests is described in his article...

Do you feel he's a really convinicing liar too, or genuine?

no just a self centered rich kid.

The "fiasco" where he held an event in a public space, then returned it to the condition in which he found it?

Wonder how big of a factor that the upstream PS4 OS codebase now using LLVM/Clang was in this decision. Even if the PS4 wasn't FreeBSD based I can see the switch making sense on it's own tbh.

Doesn't seem like any factor, there. The PS4 is using FreeBSD 9 as the kernel, which was still built with gcc.

I vouch for it being used in a very high-profile, highly concurrent online service with great results.

In this particular case we owned both the client and server-side networking libraries - but all-in-all it worked quite well and helped us deal with NAT traversal issues among other things.

i reckon this is clearly intended for non-technical business/sales people. from an software/systems engineering perspective i feel that one of the primary benefits of email is its async behaviour.

unlike IRC/IM/video/telephone/face-to-face interactions, which happen in realtime, email provides an opportunity for reflecting on conversations and responses, while also allowing people in diverse geographic areas to take part in the natural flow of a conversation.

couple this with the fact that pretty much anyone can run a mail server and communicate with any other person on the internet - i am not sure how abandoning email communication for closed systems like yammer/facebook for near-time communication would be a net positive.

having said that - adding these tools to your suite of communication formats is clearly a good thing.

pretty awesome - but that's just the UI for HAL a full replica :p

I can give a huge thumbs up for ARPnet. They are based in downtown LA (and peer @ 1 Wilshire and I think they also are part of the Any2Net exchange from CoreSite), they also fully support IPv6 on VPC's as well as managed servers.

I've had both from them and have found support to be excellent. Honestly can't say enough good things about these guys.