Almost certainly not from Slashdot. From their stats, most of their visitors are in France.
Sounds like you could replace the entangled particles with a pseudo-random number generator and get the same result.
You can't say for sure that the other party acted on the result of the particle/PRNG though. You can predict with a high degree of accuracy, but something could have changed (maybe the power went out, or the other side decided to change what happens when it reads a 1).
Searching brings up Intel, MediaTek, Broadcom and Nvidia.
The Blackphone uses an Nvidia modem; which supposedly doesn't need to share memory.
I'm assuming the Nexus 9 will use an Nvidia modem as part of their SoC as well.
I'm from Grand Rapids and studied CS here. Still haven't heard of them. Or if I did I've forgotten.
A Gamecube controller is still the best way to play Super Smash Bros. Brawl and Mario Kart Wii, IMO. But they can't be used on the newer Wii consoles and the Wii U.
(Of course I still have a Wii with Gamecube support.)
Overflows of unsigned values are well-defined in C (they wrap). (Technically the standard says unsigned values can't overflow because they're wrapped)
Overflows of signed values are undefined.
I believe you can actually update the QT libraries on Android separately using Ministro. I don't know if any other libraries do something like this.
Didn't the NSA develop SELinux specifically to compartamentalize data and prevent things like a sysadmin having more access to classified information than they need?
Unortunately multiboot does not (yet) work with this.
(Posted from Ubuntu on Nexus 7)
Apparently Google hasn't learned from HTC either.
Supposedly the new Nexus phone will have a non-removable battery, 8GB storage, and no microSD slot. (Supposedly a 16GB version will be released later).
At least it has an unlocked bootloader and fast updates, although Google does have an unfair advantage there. But don't expect them to pull the rug out from anyone.
Non DPI aware applications being marked DPI aware is Microsoft's fault. They decided to mark MFC applications (and potentially others) DPI-aware by default (at least when compiled with Visual Studio 2010).
It doesn't help that the GUI designer (at least for Windows Forms) in Visual Studio doesn't work right at non-default DPIs. It also doesn't help that their automatic scaling for Windows Forms doesn't work right (probably why they haven't enabled it by default).
I was assuming a huge part of Metro was fixing the DPI scaling issues. I guess not.
Since the books are licensed under Creative Commons, you can upload them to archive.org (see here) and redirect your users there to download.
The Nexus S 4G is part of the lawsuit.
The receipt data is first supposed to be sent to the developer's server. The server then verifies it with the app store. It's up to the developer to make sure communication with their own server is secure.
Still not a very good system IMO. What does Apple use for securing actual app purchases from their store? I'm assuming they have something in place to prevent using a MITM attack to install your own apps?
The Metro stuff doesn't run on EEE netbooks (at least the older ones) due to not meeting the minimum resolution. Trying to run it on my 10" netbook still brought up the Metro start screen, but trying to open any of the apps did nothing.