This excellent blog article describes a technique developed by Judea Pearl decades ago to do exactly this. Would be interested to understand how this is different/better.
Moving faster causes time to slow down (special relativity), but so does beeing in a deeper gravitational well (general relativity). As you move away from the Earth, both effects have opposite (but not equal) magnitude. I'm too lazy to do the math right now, but here's a walkthrough (for the case of GPS satellites, but the same equations hold; you just need to know the distance from Earth's center to Death Valley and to Mount Everest, and work out their linear velocity from that).
What was the point of Firefox? IE was free and was a proven and already well-established browser. By your logic, we never should have built Firefox and the Web should have stalled with IE6 in 2002.
The world needs a truly open mobile OS as much as it needed a truly open browser a decade ago. Android is open in name only and Google is hurriedly moving its most lucrative components into closed proprietary services and apps that aren't a part of open source Android. iOS is as closed as everything Apple does. Windows is getting some nice HTML5 support for apps, but not nearly enough. There's clearly an opportunity for HTML5 apps to compete on mobile if someone can build a solid alternative platform to the monopolies and silos we're all stuck with today.
Um, no, x86 CPUs are nothing like ARM and I'm not aware of any commercial x86 CPU with an ARM backend. Yes, modern x86 cores use a RISC-ish microcode backend with an x86 decoder frontend, but that doesn't say anything in favor of ARM. All it means is that the industry has collectively agreed that CISC as a microarchitecture is a stupid idea - not necessarily as an instruction set.
I'm not a fan of x86 myself, and I think it's a stupid design with a vast amount of baggage causing a significant power/performance impact when designing an x86 CPU (that Intel can get away with because they're a generation or two ahead of everyone else in silicon tech), but then again ARM isn't the pinnacle of RISC either (though I do think it's better than x86).
Me, I'll take whatever microarch gets the best performance per watt at whatever TDP is relevant. If Intel can pull that off with x86-64, by all means. If ARM AArch64 ends up ahead, awesome. If both are about equal, I'll take whatever's more practical based on other factors.
And since this is a camera passthrough, not an optical overlay, that's a glaring implementation flaw. Properly aligning the head tracking framerate, camera framerate, and rendering would let them render the virtual objects in lockstep with the physical ones (at least at speeds where motion blur isn't a significant issue; you can fake that by minimizing motion blur in the real image by using a short shutter time on the cameras).
I don't think the so-called slashdot effect is in effect these days except for casual and amateur sites. Pretty much any serious site can handle a hard slashdot hit any more.
So, they're locking out things that can brick the card (flash ROM/fuses, screw up thermal sensors) and apparently a hint of OS security (the Falcons that respond to userspace commands can no longer access physical memory, only virtual memory). The latter sounds somewhat bizarre, considering the firmware should be fully under the control of the driver, not userspace (I guess/hope?), but not unreasonable. Maybe there are software security reasons for this.
Nouveau is free to continue using its own free blobs or to switch to nvidia's. If they start adding restrictions that actively cripple useful features or are DRM nonsense, then I would start complaining, but so far it sounds like an attempt at protecting the hardware while maintaining manufacturing flexibility for nvidia. This isn't much different from devices which are fused at the factory with thermal parameters and with some units disabled; the only difference is that here firmware is involved.
NV seem to be turning friendlier towards nouveau, so I'd give them the benefit of the doubt. If they wanted to be evil, they would've just required signed firmware for the card to function at all. The fact that they're bothering to have non-secure modes and are only locking out very specific features suggests they're actively trying to play nicely with open source software.
You know the way to stop me, but you don't have the discipline
How many nights I prayed for this, to let my work begin
First we take Munich, then we take Turin
PS: No strike tag?
Also note that energy hungry factories are exempt from our eco tax on energy.
The price may be that they get a dog to scratch your car.