"Long Story Short" also has a credit "This Program Was Made By Humans"

The real story is how bad latency used to be. Basically it used to be easy to find yourself with 1-2 SECOND read latency in EFS. Hopefully with this and other updates these problems are now firmly in the past. https://forums.aws.amazon.com/... https://forums.aws.amazon.com/...

You're not seeing orbit precession in this video. The ground track "moves" from orbit to orbit primarily because the earth is spinning underneath a relatively stable orbit. It is true that the orbit is precessing, but it's happening much slower than you can see here. https://en.wikipedia.org/wiki/... notes that it's -3.7 degrees PER DAY. ...Whereas what is most obvious in this video is that the first orbit passes over Italy and the second over France, which is due to the -22.5 degree PER ORBIT spin of the earth below the ISS.

No. Use one of

• PBKDF2
• bcrypt
• scrypt

instead. See: http://security.stackexchange....

The rationale for http-2.0 is available in the http-bis charter. Quoting the spec:...

As part of the HTTP/2.0 work, the following issues are explicitly called out for consideration:

• * A negotiation mechanism that is capable of not only choosing between HTTP/1.x and HTTP/2.x, but also for bindings of HTTP URLs to other transports (for example).
• * Header compression (which may encompass header encoding or tokenisation)
• * Server push (which may encompass pull or other techniques)

It is expected that HTTP/2.0 will:

• * Substantially and measurably improve end-user perceived latency in most cases, over HTTP/1.1 using TCP.
• * Address the "head of line blocking" problem in HTTP.
• * Not require multiple connections to a server to enable parallelism, thus improving its use of TCP, especially regarding congestion control.
• * Retain the semantics of HTTP/1.1, leveraging existing documentation (see above), including (but not limited to) HTTP methods, status codes, URIs, and where appropriate, header fields.
• * Clearly define how HTTP/2.0 interacts with HTTP/1.x, especially in intermediaries (both 2->1 and 1->2).
• * Clearly identify any new extensibility points and policy for their appropriate use.

Mysql and MSSQL (and I assume Oracle and DB2) have had this for a while. Seems like the headline should be "PostgreSQL finally implements a feature that everybody else has had for years."

I found the problem. She skipped "one" during the countdown.

...and yet betterplace is implementing this solution with success in Europe, Israel and Japan

http://www.betterplace.com/the-solution-switch-stations

There are lots of opportunities for network hardware to introduce needless latency:

Overview:
http://www.bufferbloat.net/projects/bloat/wiki/Bufferbloat

Demo:
http://www.youtube.com/watch?v=npiG7EBzHOU

Ctrl-D Works fine in 3.5.0rc3. I just tried it.

The background colors do, indeed, stink. The funny part about the background color setter is that it changes the menubar icon to the last set color, but there doesn't seem to be a way to re-invoke it with the same color.

The article doesn't really make the case. There are two interesting charts, and one is BS (measuring Google News hits for Dragon). He is trying to draw a deep result from the fact that the NIST data he cites ends in 2002. What happened in the last eight years? Lots of arm-waving in the article, but no hard data.