![]() ![]() Chrome only gets fired up on occasion for specific tasks. If Apple did something drastic to remove extensions such as Tampermonkey, I would use Firefox as a replacement and be fairly happy with it. But, my bread n' butter is Safari because it's fast, low overhead, arguably better at privacy and Apple is only making it better with how it handles tabs, etc. That said, I still fire up Chrome on occasion because some of Google's services appear to work better when I need them. For example, I think the way Safari handles tab thumbnails is superior to not only vanilla Chrome & Firefox, but also the third party extensions that emulate Safari's tab thumbnails in Firefox. If it wasn't for Tampermonkey allowing me to run my own userscripts in Safari, I would be using Firefox instead although it has some frustrating user interface issues and is more cumbersome than Safari. I know Google has been working to make Chrome use less RAM, but I'm feeling a bit "once bitten, twice shy".įrom the limited research I've done, Safari seems less privacy-invading to me (but I could be wrong). I've also seen in the past where Chrome bloats the RAM and I find its interface more cumbersome than Safari. To do so, you simply create a UIWebView object, attach it to a window, and send it a request to load web content.Frankly, every time I fire up Chrome I feel like I'm being too heavily spied upon and tracked. Here's how Apple describes it: You use the UIWebView class to embed web content in your application. For security reasons, the browser developers get to use in their apps is a variant of an older, pre-Nitro version, called UIWebView. And developers can't use their own engines, either. This is great, if you're using Mobile Safari.īut other apps that want to include a browser function, be they Facebook or an actual alternative browser like Chrome, don't get Nitro. JIT makes Nitro faster, and Nitro makes Mobile Safari faster. ![]() The technical details aren't too important here - John Gruber has a good explanation here, if you want it - but the effects are. Mobile Safari, the default browser in iOS, uses a Javascript engine called Nitro, which in turn uses a technology called "just-in-time" compilation, or JIT, to execute scripts more quickly. And barring some kind of special exemption, it's virtually guaranteed the Chrome for iOS will have to use the same slower browser engine that Facebook has been suffering with. In the case of Safari, it is developed by Apple itself and that is why it is done with the hardware it has in mind. And this is something completely expected due to the developers of each of the browsers. So why the sudden change of course? Because in-app browsers are required to suck in iOS. In actual use of both browsers, we have to say that Safari performs slightly better than Chrome on iPhone or iPad. Until now, Facebook's app has been based on web tech - it's a browser and a mobile site inside of a blue-colored wrapper, basically. Facebook revealed yesterday that it is finally making a real, fully native iOS app. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |