Live data from Hacker News

Making Chrome better on iOS

raphaelcaixeta.com

11–20 of 68 posts

Re: Making Chrome better on iOS

#11

I have Chrome installed but don't want it as a default, this would just annoy the hell out of me.

> I have Chrome installed but don't want it as a default, this would just annoy the hell out of me.

One would assume that a developer would have this attached to an application setting.

Of course, too many settings are another problem...

Re: Making Chrome better on iOS

#13

I have Chrome installed but don't want it as a default, this would just annoy the hell out of me.

Curious, why? You don't really need more than one browser on your phone. If you installed Chrome and haven't deleted it, one can assume it's because the person prefers Chrome. Otherwise you can just delete it after having tried it out. Or am I missing something?

It can't really even be for testing, since on iOS it's not like it's possible for Chrome to render any differently than in Safari!

Re: Making Chrome better on iOS

#14
post #8

Is Chrome for iOS open source? Would there be a way to add V8 back in and release it on Cydia? That may extend the lifespan of Apple products indefinitely. My iPad 1 is already deemed obsolete by Apple and will never receive another web browser update ever, which is obviously retarded. Apple seriously needs to get that giant stick out of their ass.

a) AFAIK, no (as in, it is not open source). b) The change would not just be to mess with the JavaScript engine: it would require totally replacing out the UIWebView backend they are currently using from Apple and, well, pretty much putting back Chrome. They are not rendering the HTML, Apple's UIWebView class is; it would probably be easier to just attempt to recompile/replace JavaScriptCore system wide to stub into…

  v8 is not actually much faster
I'm not concerned about raw performance. I'm concerned with Apple forceably making iPad 1 (along with all older devices) unnecessarily obsolete by restricting the web browser on the device.

A really good example is the iPad 1 is still using an obsolete version of the WebSocket protocol. That means web servers that want to support iPad 1, must run libraries that support an outdated version of the protocol (one that contains security vaulnerabilities). The protocol can never be updated because Apple won't allow new web browsers on the device. It's a two-pronged approach which both forces obsolescense, and forces developers to needlessly add backwards compatibility layers to cover all the bases.

This is many times worse than the nightmare web developers have been facing with IE6, IE7, and IE8 support requirements because in those cases there was always the option of installing another browser, or something like Chrome-frame.

Re: Making Chrome better on iOS

#15

I have Chrome installed but don't want it as a default, this would just annoy the hell out of me.

Curious, why? You don't really need more than one browser on your phone. If you installed Chrome and haven't deleted it, one can assume it's because the person prefers Chrome. Otherwise you can just delete it after having tried it out. Or am I missing something? It can't really even be for testing, since on iOS it's not like it's possible for Chrome to render any differently than in Safari!

Given the lack of Nitro support for non-Safari browsers, you'd likely need to use another browser to better support a site which was largely JS based.

Also, for some reason I can have many 10s of tabs open to pages on Safari (with a jailbreak tweak) whereas doing the same in a non-Safari browser causes a crash.

Re: Making Chrome better on iOS

#17
I like the spirit of this idea, but I don't think the code is complete. I installed Chrome but do not want it to be my default browser. If apps started doing this, I'd just uninstall Chrome. A better choice would be to present a UIActionSheet asking the user which browser to use and then save that preference to the app's Settings bundle with NSUserDefaults.

Re: Making Chrome better on iOS

#18
post #6
post #4

I don't think this would make Chrome better but rather make every app that uses this code pretty crummy. What would make Chrome (and iOS) better would be Apple setting up some kind of default app system for links, mail, photo editing etc. Out of very few things, Intent is something that Android still has over iOS. Plus of course Chrome would be better with some Nitro on top :)

How would it make it crummy?

I may have chrome installed, but not want it to be my default browser. That is, in fact the case on my phone.

If apps started doing this, I suppose I could just delete chrome, but as with my Mac, I like having a few different browsers installed.

Re: Making Chrome better on iOS

#19
post #8

Earlier quoted context omitted.

a) AFAIK, no (as in, it is not open source). b) The change would not just be to mess with the JavaScript engine: it would require totally replacing out the UIWebView backend they are currently using from Apple and, well, pretty much putting back Chrome. They are not rendering the HTML, Apple's UIWebView class is; it would probably be easier to just attempt to recompile/replace JavaScriptCore system wide to stub into…

v8 is not actually much faster I'm not concerned about raw performance. I'm concerned with Apple forceably making iPad 1 (along with all older devices) unnecessarily obsolete by restricting the web browser on the device. A really good example is the iPad 1 is still using an obsolete version of the WebSocket protocol. That means web servers that want to support iPad 1, must run libraries that support an outdated versi…

So, an iPad 1 running the latest iOS still is stuck with an old WebSocket implementation?

If correct, that is just astoundingly crappy!

Re: Making Chrome better on iOS

#20

I like the spirit of this idea, but I don't think the code is complete. I installed Chrome but do not want it to be my default browser. If apps started doing this, I'd just uninstall Chrome. A better choice would be to present a UIActionSheet asking the user which browser to use and then save that preference to the app's Settings bundle with NSUserDefaults.

That sounds much better than just defaulting to chrome if available.

That said, this is a bit too much overhead for most developers to actually implement. For instance, you would also need to create a settings bundle, so users can reset this setting if they want.

What I'd really like to see is Apple enable this at a system level. FireFox for iOS would be nice to see, and we don't want developers to have to revisit this issue if/when it comes.

Post reply on HN