Indeed. But I'd argue Copenhagen is the one with the outlandish assumption here (instantaneous collapse on "measurement").

Re: "becoming" mainstream, don't think it's there yet: I think something over 50% of practicing physicists accept it as of a few years ago, which is a change from even a decade ago. As for other interpretations, experiments like this one are making the CI much harder to swallow - instantaneous collapse? Really? FTL signaling?

Besides, Copenhagen is just a worse explanatory framework. If we're going to make any progress on quantum computation, thinking about what's _really_ going on rather than about mysterious shadows and collapse keeps things simple, local, and deterministic (in the multiversal sense of course) But you're right that something like Cramer's Transactional Interpretation could be the cause rather than multiple worlds. I just find it hard to stomach the idea of "backward causation".

In the many-worlds interpretation of QM, also called "QM without collapse", becoming more and more mainstream, this is a straightforward consequence of entanglement. When you measure the spin or polarization of your entangled particle, you become entangled with it, so in a sense all you're doing is discovering which "universe" you're in. And of course that universe is correlated with the corresponding other particle, no matter where it is now.

The android version has literally no Undo! I tried to switch (from Evernote and/or Android Lecture Notes) but the first time I wiped something out with no undo I had to switch back.

Sure, I agree -- it's probably fast enough for most people, myself included. It's just the extra 1.5 sec of awake time (in your benchmark -- probably a lot less for real-world workflows, but if it happens on every mail sync, podcast download, it could multiply out to minutes of additional wake time per day) that bugs me because it will likely have an effect on battery life.

As hardware gets faster and (hopefully) less power-hungry, this should become less of an issue, so I expect I'll be happy to turn it on in a generation or two. I'm not there yet though. YMMV.

Whether in hardware or software, it's still a fair amount of computation, which means battery usage and latency. It has to affect the max IOPS, which means when the phone wakes up to do something, it'll stay awake for longer.

My N5's battery life is already barely acceptable; I'm not going to enable FDE on the chance it takes even a 5% or 10% hit.

Emacs does all this, or at least what I need from it, but without the weird interface. Or maybe with a weirder interface.

My experience with mine is that it's smaller than my last watch (not big), the faces are quite attractive (not ugly), and tethering to a phone isn't a bug, it's the #1 feature. I keep my phone on silent all the time now and just route the notifications to my watch. Quick glance at it during meetings to see if the email/text/whatever is important, and the phone stays in my pocket.

I started reading the paper, and get the general idea -- but haven't yet checked out the prereqs, pseudorandom spectrum permutations and flat filtering windows. Is there sample code of this algorithm available anywhere?

For only $3000 or so? It's a steal. Looks awesome, but I think I'll be watching with the naked eye this weekend.

Don't need to uninstall/reinstall. Just stop skype (well, it's probably already crashed if this is happening to you), delete the shared.xml, and restart it.

The real problem is that people are uploading their private photos to public places in the first place. It's already an invitation to crime, stalking, and government and business interference in private affairs. Why have people abandoned one of our most cherished rights so easily?

Sure, if you must upload pictures of you getting drunk or your new gadget at least strip the tags, but how about only sharing it with your friends using a more private method instead?

Works much better on natural camera images that already have some noise. At reasonably low bitrates it really is invisible.