This really has the stink of sensationalism, Ars. Xpost from another thread: I don't have any idea where the truth lies, here, but it's worth pulling the whole

This really has the stink of sensationalism, Ars. Xpost from another thread: I don't have any idea where the truth lies, here, but it's worth pulling the whole paragraph: But according to Matt Asay, who is vice president of business development for mobile Web framework maker Strobe, Apple supposedly has no plans to fix them. Instead, they are marked "not to be fixed by exec order," suggesting that a higher up at Apple is preventing engineers from fixing the problems. "Supposedly" and "suggested" let Ars weasel out of determining the truth of these assertions. Unless Apple has suddenly turned absurdly transparent, I have a hard time believing that this guy actually has any inside knowledge. On the other hand, he certainly has an incentive to bring pressure on Apple to make his business work better. Meanwhile, the author of Cydia, saurik, points out: Apple can't turn on the ability to do executable, dynamically written to memory pages just for their library: they'd have to turn it on for the entire process, at which point you could also do crazy things like download native code and execute it, bypassing the entire concept of their "codesign" mechanism. http://news.ycombinator.com/item?id=2338338 http://news.ycombinator.com/item?id=2338338 It's starting to sound less and less like Apple is doing anything shady here. Remember that RIM is having people disable JS entirely because of a WebKit exploit. This is a snarly problem.