4 ms·
"Rosenblatt queried the audience to find out how many people were iOS users, and a majority of hands went up. By contrast, when he asked how many of them were s
by niggler 14y ago
"Rosenblatt queried the audience to find out how many people were iOS users, and a majority of hands went up. By contrast, when he asked how many of them were suffering, just a few hands surfaced."
Do people expect a full browser in Firefox for iOS or a skin atop the UIWebView? If its the latter (which, as I understand it, is what Chrome for iOS is) then is Firefox for iOS really important on any level?
- objclxt 14y agoChrome for iOS is a little bit more than a skin on top of a UIWebView - the entire Chromium networking stack has been ported over. The upshot of this is that Chrome for iOS supports SPDY, whilst Mobile Safari doesn't. My understanding is that WebRTC should be going into the iOS Chrome build at some point in the future as well. A UIWebView is used for rendering, but there's a lot more Chrome code in that app than you might at first think.
- MatthewPhillips 14y agoEh, the renderer is the most important part of a browser by far. It's where all of the user-facing innovation happens.
- deleted 14y ago[deleted]
- fzzzy 14y agoYou don't think the JIT is an important part of a browser?
- MatthewPhillips 14y agoYeah, you're right, the JS engine as well a the renderer are about equally important. But I was trying to fight off the notion that Chrome for iOS is much more than a skin because it has its own network stack. It's a little more than skin, but the most important bits are off limits.
- fzzzy 14y agoThe fact that only Apple is allowed to use the JIT on iOS is a huge, huge limitation in my opinion.