6 ms·
I'm not sure a browser's <video> tag not supporting all the features this guy wants makes the iPad "the new IE6." Seems more than a little hyperbolic to me. <vi
by chc 16y ago
I'm not sure a browser's <video> tag not supporting all the features this guy wants makes the iPad "the new IE6." Seems more than a little hyperbolic to me. <video> is one of the shakiest parts of HTML5 in general, particularly with the whole codec thing.
- ycreject 16y agoSeconded, the iPad and iPhone actually have wayyyy better support for a lot of HTML5 things like CSS 3D transforms than any other browser (Chrome included).
- patrickaljord 16y ago[Reference needed].
- ycreject 16y agohttp://webkit.org/blog/386/3d-transforms/ http://webkit.org/blog/386/3d-transforms/ Try those examples on Chrome or Android (or probably anything else, but the CSS attributes are all -webkit prefixed so comparing against FF would be silly). Chrome is just now rolling out GPU acceleration so they might actually work on some platforms but previously they (meaning Chrome and Android) were using a rendering engine called Skia and were dropping out a bunch of the perspective matrix therefore making it strictly affine and preventing any true depth effects.
- badmonkey0001 16y agoI'll bite: The problem with the implementation is plain to see: -webkit-transform: rotateY(45deg); That's a proprietary CSS declaration. It's exactly the same kind of "embrace and extend" kind of stuff that entrenched IE6 so long ago and severly splintered web development. Why, oh why, do I have to prefix -moz- or -webkit- onto CSS instructions in a "standards compliant" world? Web dev is getting badly fractured again. There was a point of stability about two years ago where all of the IE quirks were knowns and the rest of the browsers followed CSS2/HTML4 fairly consistently. There was a blissful period where you knew something might be borked in IE6, but could almost just assume things would render in most other browsers. Such a time has now ended. I find myself saying "but that should have worked?!?!" at about the same rate I did when IE6 was new 10 years ago. Sadly now I have to have $$ to spend on testing hardware rather than just firing up an old piece of software. TL;DR, 3D transform in webkit isn't true CSS3... it's a proprietary webkit feature.
- ryanf 16y agohttp://www.w3.org/TR/css3-3d-transforms/ http://www.w3.org/TR/css3-3d-transforms/
- ugh 16y agoBrowser prefixes are often misunderstood. There are very good reasons for using them, A List Apart has a nice article about them: http://www.alistapart.com/articles/prefix-or-posthack/ http://www.alistapart.com/articles/prefix-or-posthack/
- bzbarsky 16y agoYes, but 3D transform is still a proprietary webkit feature, which was badmonkey0001's point. The fact that they wrote up half-assed incomplete documentation of it and submitted it to the W3C for consideration as a standard doesn't change that. It's actually more or less like OOXML except it hasn't had the feedback-and-rubberstamp process happen yet. With any luck, that process won't happen, in fact (in that there will be actual discussion and actual specification, not rubberstamping). Now if the CSS working group actually starts actively working on 3D transforms (hasn't happened yet) and anyone other than Webkit actually implements them, then we can talk about them being something other than what they are now. There _is_ a bit of confusion here because vendor prefixes are used for both experimental implementations of CSS working group proposals and totally random proprietary gunk. The problem is telling the two apart... ;)
- ugh 16y agoBrowsers sometimes charge ahead. I woul them rather to do that with prefixes than without. I don't think that's in any way comparable to Microsoft's behavior.
- bzbarsky 16y agoCharging ahead with prefixes is sure better than without. Doing that and encouraging web authors to create public-facing sites that depend on the prefixes to work correctly (which is what Apple has been doing) is no different from Microsoft's behavior around 2001, imo.
- patrickaljord 16y agoSo Safari has 3d-transform, Chrome has file reader and writer api and webgl which safari doesn't. It's easy to cherry pick.
- Jacob4u2 16y agoI agree. This seems more like a "rage quit" post than a reasonable/rational response to the challenges of multi-platform development.
- ugh 16y agoThat comparison is just badly chosen and unnecessary [0]. He argues that some aspects of iOS are a little bit like aspects of IE6, not that the “iPad is the new IE6”. Writing that as the headline is just asking for trouble and will only lead to people not discussing the substance of your article but screaming at each other. I’m all for just ignoring that comparison and focusing on the substance of the article. Please. (Because the substance, unlike the comparison, is actually interesting.) [0] Some would call it “linkbait”. And yes, this was a very lame attempt of trying to get away with using a word I usually hold in contempt. Shame on me.
- pyre 16y ago> this was a very lame attempt of trying to get away with > using a word I usually hold in contempt Why not use a more general term then? Surely this practice pre-dates the internet (and therefore also the term 'linkbait').
- ugh 16y agoSensationalism and hyperbole are probably the right words.
- j_baker 16y agoThe headline is the substance of the article, like it or not. I mean, do you blame people for arguing that the iPad isn't the new IE 6 when the title of the article is "iPad is the new IE 6"?
- ugh 16y agoI can’t really blame them, no, but HN has a penchant for turning hyperbole and sensationalism into good discussions. From time to time.