On the back end, if you must store passwords, make sure they are hashed using a modern secure algorithm (AES-256, SHA-2 or SHA-3) and salted, and do that as soon as possible in your back-end processes. No, your users do not need a way to recover >
No. Use one of
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:
It is expected that HTTP/2.0 will:
Why not make the batteries replaceable? Just switch them as a gas station, simple.
Because it's a stupid idea for reasons we've covered numerous times before.
...and yet betterplace is implementing this solution with success in Europe, Israel and Japan
There are lots of opportunities for network hardware to introduce needless latency:
Overview:
http://www.bufferbloat.net/projects/bloat/wiki/Bufferbloat
There's still a number of key combinations that Calc is missing (most noticeably ctrl-D to copy cell above), and the background color tool is still horribly designed (only contains colors too dark for use as a background, and it does not remember the last chosen color). It's simple stuff like this that keeps people on Excel.
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.
"Card readers? We don't need no stinking card readers." -- Peter da Silva (at the National Academy of Sciencies, 1965, in a particularly vivid fantasy)