4 ms·

Gruber: It is not an oversight or a bug, or the result of a single person at Apple wishing to hinder the performance of web apps. Ars: Apple is aware of the is

by aphyr 16y ago

Gruber: It is not an oversight or a bug, or the result of a single person at Apple wishing to hinder the performance of web apps. Ars: Apple is aware of the issues, which are currently filed as bugs... are marked "not to be fixed by exec order," Well, this ought to be interesting.

deleted 16y ago
[deleted]
danilocampos 16y ago
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.
- kanja 16y ago
  AFAIK strobe is made up mostly of ex-apple people - furthermore, they knew about the "bugs" at least a month ago - Charles Jolley was talking about them at the most recent sproutcore nyc meetup. I don't think it's unreasonable to believe the truth of these assertions.
sammcd 16y ago
I don't see how these two points are mutually exclusive. It very well could be an executive order not fix it because of the security issue.
- Me1000 16y ago
  The problem is that if the issue never gets fixed then native apps using a webview will never see this performance improvement. Which means in order to stay competitive Apple must continue to develop nitro. Which means they'll either develop nitro in parallel with the old JS engine, or they'll let the webview stagnate. Marking an issue as "dont fix" is very scary indeed for the web on iOS.
ra88it 16y ago
If they're indeed marked "don't fix", that's probably because they are intentional. They aren't bugs.

by aphyr 16y ago

deleted 16y ago

[deleted]

danilocampos 16y ago

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.

kanja 16y ago
AFAIK strobe is made up mostly of ex-apple people - furthermore, they knew about the "bugs" at least a month ago - Charles Jolley was talking about them at the most recent sproutcore nyc meetup. I don't think it's unreasonable to believe the truth of these assertions.

sammcd 16y ago

I don't see how these two points are mutually exclusive. It very well could be an executive order not fix it because of the security issue.

Me1000 16y ago
The problem is that if the issue never gets fixed then native apps using a webview will never see this performance improvement. Which means in order to stay competitive Apple must continue to develop nitro. Which means they'll either develop nitro in parallel with the old JS engine, or they'll let the webview stagnate. Marking an issue as "dont fix" is very scary indeed for the web on iOS.

ra88it 16y ago

If they're indeed marked "don't fix", that's probably because they are intentional. They aren't bugs.