51–60 of 97 posts
However it should be fast enough for ebook production, if the typography is done right.
Lets get this straight, the limitations in performance on Mobile Safari are very much deliberate limitations. Do you seriously think a company like Apple who gets a pretty large chunk of app store sales is going to let something like HTML5, CSS3 and Javascript steal it's profits away? Fat chance. Although it even rings true for desktop browsers not being able to perform as optimally in regards to some HTML5 features…
Earlier quoted context omitted.
On Android, you can install updated browsers like Firefox and Chrome. Not sure about how well their mobile counter-parts actually support HTML5, but at least you have a choice for a non-system-supplied browser. On iOS you are, as you say, SOL because Apple has literally crippled the options you have down to one: The one they supply and update, once a year.
>On iOS you are, as you say, SOL because Apple has literally crippled the options you have down to one: The one they supply and update, once a year Especially egregious given Steve Jobs' memo about not supporting Flash on iOS. http://www.apple.com/hotnews/thoughts-on-flash/ Some choice quotes: >Though the operating system for the iPhone, iPod and iPad is proprietary, we strongly believe that all standards pertaining…
Well, noticed how Android's own web browser is even worse in HTML5 than Mobile Safari? And this is Google, the guys that really like mobile html5 apps.
Fact is, it's not that easy to make a good mobile browser --heck, it's not that easy to make a good desktop browser.
Still, desktop HTML5 leaves a lot to be desired. Forms support is lacking, the audio side is neglected, SVG still lacks features and is not properly accelerated (even the latest IE that just got it is better in this regard), the client side storage didn't pan out well, typography is still crappy, etc. And this is for the desktop, that doesn't have the battery, memory and performance concerns of the mobile.
And it holds true for Safari, Chrome AND Firefox.
So, in case you're thinking Apple is doing something especially malicious here, well, they are not.
Those of you surprised that HTML5 may not soon (if ever) be the holy grail have been drinking too much cool-aid.
Earlier quoted context omitted.
Did you notice the enormous performance improvement in Facebook's app when they moved away from that type of solution to a native one?
That´s really wrong! Facebook still uses a lot of HTML5 in their new App! But they fixed a lot of bugs, mainly removed a lot of concurrent UIWebViews. For more information, take a look at: http://www.vasantkumar.ca/2012/08/native-vs-html5-why-facebo... But simply saying "They removed HTML5 and all works a lot better" is very wrong.
Saying HTML5 won't be 'production ready' for a while, and saying that HTML5 will never be production ready are two very different things, but I feel people conflate the arguments all the time. If you do believe that HTML5 will eventually be production ready, even if not for another 2 years, ask yourself this: when that time comes, do you want to be the guy with 2 years experience or the guy with none? When the indust…
Sadly, Apple and/or Google have the power to retard the adoption of HTML5 as long as they like. "But ender7," you say, "both Mobile Safari and Chrome have great support for HTML5." Yes, they do. Sort of. Except for the crippling bugs in many of their implementations. Some of these bugs render the APIs in question essentially useless on mobile. Or just a giant pain in the ass to work around. Or have performance issues…
Which browser is the shining beacon of light for HTML5?
Earlier quoted context omitted.
>On iOS you are, as you say, SOL because Apple has literally crippled the options you have down to one: The one they supply and update, once a year Especially egregious given Steve Jobs' memo about not supporting Flash on iOS. http://www.apple.com/hotnews/thoughts-on-flash/ Some choice quotes: >Though the operating system for the iPhone, iPod and iPad is proprietary, we strongly believe that all standards pertaining…
> It's been two and a half years since that, and still HTML5 has major issues. Given Apple's engineering prowess, I doubt that HTML5 is a priority for them, or else they would've had a great implementation by now. Well, noticed how Android's own web browser is even worse in HTML5 than Mobile Safari? And this is Google, the guys that really like mobile html5 apps. Fact is, it's not that easy to make a good mobile brow…
"Android's browser"? Care to elaborate on which browser that is?
The one built from source? Which version of the source would that be? Or would it be Chrome? Or Firefox? Or Opera? Or Dolphin? Or Maxthon? or MIUI browser? Or the one included with TouchWiz? In which case, which version of Touchwiz?
And how is it "even worse"? You mean it doesn't behave like Mobile iOS Safari so that sites specifically tailored for iOS-devices doesn't work out of the box on Android? What a shock that is, eh? It's almost like I write sites specifically for MSIE, and they don't render correctly in Firefox. Haven't we heard about this story once before?
I'm not debating the correctness of your statement, but when you start out with something as mindblowingly pointless as "Android's browser is even worse" it's hard to take the rest of your point seriously.
Lets get this straight, the limitations in performance on Mobile Safari are very much deliberate limitations. Do you seriously think a company like Apple who gets a pretty large chunk of app store sales is going to let something like HTML5, CSS3 and Javascript steal it's profits away? Fat chance. Although it even rings true for desktop browsers not being able to perform as optimally in regards to some HTML5 features…