setx /?

setx path "%path%;new_dir" /m

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)

Reasonably sized fans wouldn't work in Martian atmosphere..

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.

It's handled when your push service trims out dead tokens, which it needs to do periodically anyway.

Thanks for that info, I somehow overlooked this when rolling my own push provider.

For those still interested: There is a separate feedback service (feedback.push.apple.com) that providers should query periodically. It returns a list of device tokens that are no longer valid for your application.

Reference: http://developer.apple.com/library/ios/#documentation/Networ...

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.

There is always a reason to not rewrite something once it is released and operational: there are almost certainly other things you can be doing that would provide higher value.

(Also, I am reasonably certain that the issues you are eluding to with Cydia not working correctly on iOS 4.0b* were, as usual, WebKit issues, which I specifically admitted in my post: and, in fact, during 4.x is when I came up with a much simpler way to handle that specific implementation detail. That said, looking through my git repository, the only changes I seem to have made for 4.0 seem to be to things that fundamentally are not public APIs: restarting SpringBoard being the major one.)

It was 4.2b, my bad. Cydia was using some UI class from a private framework that got removed in 4.2 betas.

Yeah, there was _UISwitchSlider class or something being used. I ripped almost all of that stuff out for "Cydia 1.1"; except for saurik's WebKit code to replace the crippled UIWebView, it's almost entirely public APIs now (UIViewController, UISwitch, etc).