They have LiDAR, GPS, radars, inertial reference unit, steering wheel angle sensor and high-precision odometry (left rear wheel rotation sensor). Afaik, LiDAR/map convergence is actually used for localization.. at least it's the case for the street view car, per http://www.youtube.com/watch?v=kdPwaWATYKg&feature=plcp
OS X/iOS use a 'sandbox' driver that utilizes TrustedBSD MAC infrastructure ( https://developer.apple.com/library/mac/#documentation/Darwi... ).
Basically, most system calls can be verified against one or more policy modules, and blocked if non-compliant.
Not really possible with Windows and its bajillion of syscalls (1000 in win32k alone afair)
Third level in proper browsers:
1. Open a JS debug console (Cmd+Option+J)
2. Set a breakpoint on window load (Event Listener Breakpoints - Load - load).
3. Reload the page
4. After the breakpoint is hit, type
localStorage.setItem('msIsSiteModeActivated', 'true'); navigator = {appName: 'Microsoft Internet Explorer', userAgent: 'MSIE 9.0'};
5. Disable the breakpoint, level 3 should now work..
"Since I was running Windows on a Mac with Parallels it was uneasy to hit "printscreen" while the game was running. I hardcoded the '*' from the keypad to produce the same"
Umm.. educational, sure, but can't you just:
alias +shift "bind 8 screenshot";
alias -shift "bind 8 whatever_was_bound_to_8";
bind shift +shift;
Multicore does nothing for raw io rate, but they're using compression, and the claim seems to be that they can use higher compression levels and still be faster than an SSD (so that decompression throughput won't be a bottleneck).
Even without inlining, it will be subject to tail call elimination with any sane compiler: my_tmpfile will just branch to _imp_tmpfile instead or returning.
I recall Cydia being pretty broken in iOS 4 beta days, and using undocumented APIs for no reason (it was obviously written before the public SDK, but there was no reason NOT to rewrite it once the SDK was out).. So that seems pretty hypocritical of you to want Apple to 'weed out' apps using a special environment that app can't even be tested against by the dev. Also, average iOS app lifetime isn't long enough to even remotely justify such draconic testing measures - most will be out of the app store charts long before there's a breaking change in iOS.
Maybe Apple doesn't block beta reviews because it incentivizes developers to fix their apps before the release? Most of those problems should be trivial to at least work around with version-dependent logic to minimizes regressions on versions < 5.x.
Bad reviews don't exactly hurt Apple, and it's not like iOS developers are scarce these days, so it might just be Apple having their priorities set straight (users > devs) and not a coding blunder..or maybe it's just me overthinking it.
setx path "%path%;new_dir" /m