4 ms·

The title is totally unfair. If iOS 3.x was still widely used in 2020, then the title would be justified. > HTML wasn’t created for dynamic/interactive content

by Yaggo 16y ago

The title is totally unfair. If iOS 3.x was still widely used in 2020, then the title would be justified. > HTML wasn’t created for dynamic/interactive content, it was created to present academic documents. Yep, and the internet was not created for porn, PTFE not for cookware, etc. Technologies evolve. > JavaScript performance on iOS is 100x worse than desktop. No doubt and that's unlikely to change. iPad uses about ~100 times less power than typical desktop. > Canvas performance on iOS is so bad that it is barely usable. Not hardware accelerated == slow on mobile. Hopefully the canvas will be accelerated, too. > A lot of people don’t upgrade their software, iOS 3.2 is completely different than iOS 4.2 and you should support both. Should you? We are talking about consumer devices. I think it's totally fair to ask the user to upgrade their platform (OS/browser) to get new features (it's free!). That's what Apple is doing, anyway. > The iOS simulator is different than the actual device. I agree, would be nice if it emulated the actual performance of iDevice. > It is very important to note that every single Webkit browser works differently and -- That's the curse (or blessing?) of an open source project. Still, WebKit browsers (eg. Chrome / Safari) differs less than totally different browser engines. Would you be happier if Chrome had come up with their own engine? > -- that older versions of the iOS has many bugs and missing features (the new ones as well). No shit? > Chrome and Safari have a bunch of rendering problems related with HTML5 video and CSS3 as well when you start overlaying content and adding CSS transitions. No doubt. That's the price you pay for having multiple implementations of (loose) spec created by multiple participants. Which is still far more better situation than having one closed implementation created by a single company for few selected platforms (partially substandard runtimes). > Android 2.0-2.2 also have many bugs related with HTML5 video. Not iPad's fault. > Apple bug tracker sucks, you can’t even see if anyone reported the same bug before, I won’t post anything there because of that and because I don’t agree with the company policy… - Apparently Apple too suffers from "big company" syndrome. > If you are a jerk, I will be a jerk with you as well… Nice attitude. > If it works well the end user will not care about which technology was used to create it. Users have no clue, no news here. > Don’t believe in keynotes, even better, don’t watch them… Whether you consider it "amazing" or not, arguably Safari for iOS offers the best browsing experience today in its class (handheld devices) and Apple has advanced HTML technology a great leap forward.

brudgers 16y ago
The analogy to IE6 is based on both requiring substantial duplication of effort in order to render the page similarly to its appearance in other browsers and to provide like functionality to web sites. It seems to me that in part, Apple's intention is to make it less troublesome to develop and maintain an app than it is to develop and maintain a rich media website which handles iOS gracefully through the deliberate incorporation of incompatibilities in the iOS browser (e.g. no Flash). [edit] incompatibilities are different from non-compliance with standards.
recoiledsnake 16y ago
>> Canvas performance on iOS is so bad that it is barely usable. >Not hardware accelerated == slow on mobile. Hopefully the canvas will be accelerated, too. I thought canvas was one of the biggest reasons that HTML5 would eliminate the need for Flash. I think it is disingenuous to say that the iPad does not need Flash because it supports HTML5 when the HTML5 support is in such a bad shape. Canvas will be hardware accelerated even in IE9, Apple has no excuse here. Anyway, I guess it's no surprise that Apple does not have much interest in improving HTML5 support for the iDevices, after all they have a vested interest in people developing apps instead. They get their 30% cut, the app does not work on other platforms (unlike HTML5), and they get their cut of iAds and any another purchases.

by Yaggo 16y ago

brudgers 16y ago

The analogy to IE6 is based on both requiring substantial duplication of effort in order to render the page similarly to its appearance in other browsers and to provide like functionality to web sites. It seems to me that in part, Apple's intention is to make it less troublesome to develop and maintain an app than it is to develop and maintain a rich media website which handles iOS gracefully through the deliberate incorporation of incompatibilities in the iOS browser (e.g. no Flash). [edit] incompatibilities are different from non-compliance with standards.

recoiledsnake 16y ago

>> Canvas performance on iOS is so bad that it is barely usable. >Not hardware accelerated == slow on mobile. Hopefully the canvas will be accelerated, too. I thought canvas was one of the biggest reasons that HTML5 would eliminate the need for Flash. I think it is disingenuous to say that the iPad does not need Flash because it supports HTML5 when the HTML5 support is in such a bad shape. Canvas will be hardware accelerated even in IE9, Apple has no excuse here. Anyway, I guess it's no surprise that Apple does not have much interest in improving HTML5 support for the iDevices, after all they have a vested interest in people developing apps instead. They get their 30% cut, the app does not work on other platforms (unlike HTML5), and they get their cut of iAds and any another purchases.