Comment Re:Now patched? (Score 4, Informative) 306
No patch is currently available -- a fully patched 10.5.7 system remains vulnerable. See also http://landonf.bikemonkey.org/code/macosx/CVE-2008-5353.20090519.html
No patch is currently available -- a fully patched 10.5.7 system remains vulnerable. See also http://landonf.bikemonkey.org/code/macosx/CVE-2008-5353.20090519.html
In addition to disabling Java support, Safari's 'Open "safe" files after downloading' must also be disabled to prevent websites from automatically loading a Java WebStart application via a JNLP file.
I've also posted a demonstration of the vulnerability at http://landonf.bikemonkey.org/code/macosx/CVE-2008-5353.20090519.html
1. Nobody calls it "Frisco."
Tell that to Hardee's
"Hardee's is a restaurant chain, located mostly in the Midwest United States and Southeast regions." Ah yes, the good ol' midwest.
Instead, look at fairsoftware.net (hey, if I invented it, I can brag about it). You won't earn immediate cash, instead you'll be getting equity into whatever fun software project you find. Or start your own and get more geeks to join you, also for revenue share, not upfront cash.
This is very, very cool.
Do you have any plans to support existing legal entities using FairSoftware? This would provide us with a low-friction approach to collaboration, allowing trust and more permanent relationships to form organically between independent contractors and our organization.
Also, do you have any thoughts on models where external billing is required, such as the iPhone App Store? Serving as a publisher could be one option here (and would be a fairly significant advantage given the difficulties individuals often have dealing with the app store). That's something I'd definitely be interested in collaborating on.
Lastly, a related project -- have you seen One-click Organizations? The information was here, but the the webhost has gone kaput today, so here's the Google Cache version
Commenting to remove accidental redundant moderation. It's right next to "Insightful".
Sorry!
Since I'm here -- I've always though that the "hardware is cheap, programmers are expensive" position presented a false dichotomy: a choice between achieving passable performance through good design, versus optimizing for developer efficiency. Efficient use of resources and ease of development are not mutually exclusive.
Modern mobile devices have fast CPUs yet very limited RAM. And no swap.
They have faster CPUs than they used to. The CPUs are still not "fast".
I spent the last week implementing, profiling, and improving up disk-backed image caching with a front-end LRU memory cache for the iPhone, and experimenting with offloading batch image processing off to a OpenGL FBO. Doing image interpolation while scaling is so expensive on the iPhone's relatively fast CPU that it's absolutely necessary for me to cache thumbnails.
The cache implementations themselves had to be highly optimized in order to pull images off disk fast enough to run inside of a tight animation loop, while also supporting a background thread rendering of not-yet-cached thumbnail images and saving to the disk cache.
I can't even fathom writing this in Python. Any spare CPU I have, I put to good use -- there's absolutely none available to spend on a slow interpreter, even for non "performance critical" parts. If there's a non-performance critical code path, then I can always use any available CPU time to do more background work and achieve better perceived UI performance.
"Never give in. Never give in. Never. Never. Never." -- Winston Churchill