I guess I should finish my sentences...

...may be the same of previous passwords.

One can do the same with public/private key pairs. Just, instead of a password, give them a specific public key. Refresh that at will. The only thing necessary, as one should not want to keep keypairs around, is a good HW implementation which integrates with browsers.

How else can you mandate a password policy that requires that no more than 3 characters may be the same...

And they use lasers these days (in their INS).

Interesting to hear that they do not have phased array GPS receivers...

I'll give you dead pixels, on CRT as wel btw. As for the strain: I can watch 12 hrs with LCD and about 8 with CRT (Iiyama vision master 510, 85 Hz). It may be dust related (dust parts on the monitor get propelled at anything in front of them because of the static charge).

At least one of the problems is that people, including myself, are less social when driving a car. A black box can help people remember that antisocial behaviour is not forgotten (especially when an accident happens). I would however legislate a mandatory warning sticker, clearly visible for the driver.

The only thing I've seen failing on an LCD is the power button. Second, it is much less strain on my eyes, directly measurable in hours / day.

You also have double fibers?

The problem is not the hardware but the software. The hardware has been parallel for ages, even locally (GPU, GPU-memory, CPU, memory, HDD, DMA - memory processor, ...).

Software is a different problem across networked/parallel arena. If you really think about an SMS it is not much more than 'hello world'. You type it and you see text (no other function, other than transport which isn't really a function, has been done) and testing it should be easy. This is not even about parallelism but about communication.

The best way to create software for networking is to not re-write it for all these new parallel architectures/internet (which means you compile it for compartimented execution). This is however, pretty hard to do (I don't know about such an implementation). The alternative is that everybody needs to put all the same glue in its software over and over (RMI, OpenMP, ...). We are doing #2.

By the way I think there is a big difference between networking, which has a premise that things fail, and local transport of data/code which is specced on its workings. Fundamentally different (price).