I do, actually. Well, they're more partners than customers, since we give them our code and they sell it. But, yes, I have a lot of meetings with outside parties. We convince about half of them to join our Hangouts from their laptops, the others we add to the meeting via phone. Outside of meetings, we communicate entirely via e-mail. Voicemail is still irrelevant.

At IBM, my role was entirely customer-facing. Voicemail was still fairly rare, though teleconferences were the norm. Most communication was, again, via e-mail or face to face.

our governments love bogey men, someone who they can point at and make us forget their own faults or to use as an excuse for more spending on the military/spy-agencies/... We have been here before, anyone remember how Saddam was supposed to have WMD (in spite of doubts from Hans Blix), Tony Blair's ''dodgy dossier''. Finding other examples is not hard.

Time will (probably) tell if it was/wasn't NK - but by then the difference will not make a story.

Personally I haven't made it to stateless yet. People still address me as CDIR, but your point still remains.

Are they guaranteeing throughput? Then it's meaningless for most folks. It's like putting tires rated for 200 MPH on your care and assuming it will now go 200 MPH.

Presidents, governors and mayors all do this kind of thing -- call up private businesses and ask them to do stuff. The mayor may call a local business and ask it to reconsider withdrawing its sponsorship of the local youth baseball league. The governor might call up union leaders and senior management in a strike, particularly if it affects things lots of people need like transit or health care.

This is the exercise of *soft* power, of influence rather than of compulsion. Obama can't call Apple and compel them to change their stance. But he can call Tim Cook and *persuade* him, possibly with more success than Michael Lynton, particuarly given that the two may be having some kind of dispute. Ego *does* play a role in CEO decision making.

Ie what is the ping round trip time to the ISP's router ? With an interactive protocol/application round trip time is as important as bandwidth.

... you are an idiot.

You're going to see the cops as being bad and wrong and evil even as they save your life.

Its mind numbing that you don't understand why that turned out the way it did.

And for reference, normal health people don't die from a chokehold thats released as soon as the person loses conscious, fat ass had a heart attack due to his own health issues.

Not if adjacent rows are being heavily, cyclicly read.

Where I work (Google), telephone calls are all but dead and voicemail is completely dead. Pretty much everyone lists their personal mobile number as their phone number in the directory (or a Google Voice number that forwards to their mobile), because getting business calls at home or whatever is a non-issue because no one makes phone calls for business. Communication is via e-mail (for formal communications, messages that don't seek quick response, or group distribution), instant message (for short, timely discussions) or face to face/video conference (Google Hangout). Some groups, especially SREs (Site Reliability Engineers -- sysadmins, more or less), also use IRC, mostly because it stays up when other stuff breaks.

Further, the etiquette is that nearly all non-email communication starts with an instant message. This is true even if the other party is sitting right next to you, unless you can tell by looking that they aren't deeply focused on something. There are only two times a phone is used, one rare, the other extraordinarily rare, and in neither case would voicemail even be useful.

The rare case is for a (generally informal) meeting when one party for some reason doesn't have access to Hangouts. The extraordinarily rare case is when something is on fire and someone's attention is needed at 2 AM Sunday morning. The latter has never happened to me, though I have called a couple of colleagues. Even then, a phone call is an unusual step; normally you wake people up via the pager system (whose messages are delivered via various means, sometimes including automated phone calls) and proceed to communicate via IM or VC.

It's not just Google, either. Prior to Google I worked at IBM which where communication similarly revolved primarily around IM and e-mail, though meetings were primarily via teleconference, not video conference.

From what I can see, voice is generally declining, and voicemail is leading the charge.

If you're interested in stable and secure, you're already not using Docker, so problem solved.

The problem with insisting that everything has to be well thought out and planned first is that gets in the way of innovation, and things slow way down while you do your planning. But while you're spending a couple years trying to plan out the project and account for every use case and vulnerability, by the time you've written the code, it's already out of date and not useful, so the planning has to start over again.

If you want to apply NASA level of planning and diligence where a software project can take years (or even decades), you should feel free to use only tried-and-true solutions. Maybe an IBM mainframe will give you what you're looking for. But don't insist that the entire world needs to stop to meet your needs for stability and security.

Err. Rocket is from the guys that brought you CoreOS. CoreOS uses systemd. Not the same thing.

Upstream verification won't help. The client has to verify that the image it received is the same one the server verified, otherwise someone can hack a router to silently redirect the client to a malicious server and serve up whatever image they want alongside a copy of the signed manifest for the official image and you're fsckd. What they need is:

1. The manifest has to be signed.
2. The manifest has to contain a secure checksum (cryptographic hash) of the official image the server has.
3. The client has to verify the signature of the manifest to confirm that the manifest hasn't been altered and comes from the official source.
4. The client has to verify that the checksum of the image it received matches the checksum for the image in the manifest.

5. Step 4 is apparently what's missing from the client.

But he did film it, kinda. He just didn't put it into the story. It shows up a little bit in the Mirror of Galadriel sequence.

One could argue that that was the correct way to play it, too. I know people who claim to have "walked out of the theater after the first ending and skipped all of the other ones," as it is.