Gary_W_Longsine
Gary_W_Longsine on Hacker News
If you want to join the TestFlight which will start within the next few days, find @illumineX on Twitter.
(I founded illumineX in 1998, and iBlogger was one of the first apps on the iPhone App Store in 2008.)
You wrote: "I've watched multiple videos where data transfer rates dropped significantly when the antennae are touched in the same way making me think this is not just a software problem."
-- quote -- by user: austingaijin The yellow blotches will disappear Apple is using a bonding agent called Organofunctional Silane Z-6011 to bond the layers of glass. Apparently, Apple (or more likely Foxconn) is shipping these products so quickly that the evaporation process is not complete. However, after one or two days of use, especially with the screen on, will complete the evaporation process and the yellow "blotches" will disappear.
How do I know? I was involved in pitching Z-6011 to Apple. -- end quote--
Regarding the scheduler, I'm not sure enough details are known outside of Apple at this point to know what the results would be on Snow Leopard. Your milage would obviously vary when porting to some other OS. It's easy to imagine that running a PThreads app might hog some cores, or be punished inappropriately by the scheduler. These things can happen when running more than one threaded app on a system today, without GCD. This behavior, even if not documented, should be relatively easy to explore with some simple demo apps, though, without porting your entire app.
And, uhm... you will need to refactor your application to take advantage of the new API. (Was that a trick question?) Apple's guidance indicates that you can make modest changes for big gains by focusing the refactoring effort on the parts of the app that do the most computationally. For some apps this can be a small amount of work for a large gain, particularly if you can take advantage of OpenCL as well as GCD.