Apple HTML5 showcase
- Started
- Last post
- 74 Responses
- hotroddy0
Doesn't work in Firefox, Chrome, nor IE. What a joke! If you have to download safari isn't that (*dare I say it) like downloading a plugin?????
- yeah, but i think the point the other are try to make is that this *is* kinda for safari only since they don't have flash.SteveJobs
- *i think*SteveJobs
- you still utterly fail to grasp this concept.acescence
- concept: can't use it if I'm trying to develop for multiple browsershotroddy
- you're right, but then no one is claiming such. it's an emerging standard. not complete. get it?acescence
- a lot of these things will work in modern browsers, just not all for reasons you can read in my other postsacescence
- so in fact, you could use much of it. the reason safari is required here is that not all features are supported by all browsers,acescence
- so it would be a broken experience.acescence
- anyway, yeah, like downloading a plugin, except nothing like it. so congrats on that statement of brillianceacescence
- it's great to see that qbn support my safari plugin though. works pretty seamlessly, i'd have no idea i was locked inacescence
- was locked in if you hadn't enlightened meacescence
- SteveJobs0
Der durker duuuurrrr!!!!!111
- ukit0
- SteveJobs0
sorry everyone, i have some bad news
- ukit0
To be fair they don't hold a candle to the Adobe HTML5 demos...oh wait.
- hotroddy0
I think it's a little naive to think all browsers are going to embrace one form of HTML5 and thus making designer's/developer's lives easy. Developing cross browser sites is going to be harder in the future as javascript methods and classes become more sophisticated. These demos are intended so that ipad users can have the rich browsing experience which it's current lacking. Do you think Microsoft is going to support something created specifically for the ipad? Our jobs are becoming increasingly more difficult in the fractured web medium. This is what made flash so darn attractive and it's only getting worse.
- CyBrain0
I get that HTML5 has a future. I'm not going to say it's a Flash killer, but it will NEVER be standard and the same across all browsers. You know...like Flash has been for about 14 years.
The only thing I see here is that HTML5 is severely more limited than Flash and no doubt MUCH harder to implement.
- SteveJobs0
apple's demo's and timing make perfect sense. they've gone and stirred up a storm and created a fierce rivalry between these two technologies, as well as a LOT of hype, and now, in order to keep the momentum going they have to meet everyone's already quite high expectations.
at this point it's literally a matter of them being the first to provide full-on html5 support. otherwise, they'd be called out on it, and boy would thier faces be red!
the only problem i see is while there is certainly a lot of excitement around html5, there's still not a lot of it used in mainstream - which is not surprising. it would be a bold, and probably idiotic move to adopt a technology that's not yet supported on every, or at least most browsers.
what's so funny about this is everyone's perspective. steve jobs essentially presented this as an either/or and it seems like nobody can see it any other way. it's like somone starts claiming that trucks are dated and cars are the future, and then everyone exhausts themselves debating which is a better option, and that one must go away!
i'm beginning to sound like a broken record on this topic, but there's no reason the two technologies cannot co-exist and compliment one another. they each have their strengths and over time, one will prove itself better in one area than the other, but it is VERY unlikely that one will ever supplant the other.
- SteveJobs0
just out of curiosity, how many of you are using html5 right now in your projects? and i'm not talking about your portfolio's or the 'experiments' section of your site. i'm talking about corporate, public-facing work that reaches millions of visitors.
also, how many of you have been porting flash-based applications to html5?
- SteveJobs0
sorry, guess i should have also stated, not iphone/ipad-only. clearly those projects will thrive.
- SteveJobs0
just curious as ie still holds about a third of the market
IE8,IE7,IE6: 16.0% 9.1% 7.1% (32.2% total)
Firefox: 46.9%
Chrome: 14.5%
Safari: 3.5%
Opera: 2.2%
- ukit0
Right, and that's why using HTML5, in the near future, I think will come down to either:
(a) targeting niche audience - iPad, iPed
(b) using solutions that have figured out a way to provide backwards compatibility with IEYou might scoff at that second one but it's actually becoming more and more feasible thanks to efforts of companies like Google.
- i don't scoff at it. i'm using excanvas, but at the same time, it's still quite limiting as the who api isn't supported with itSteveJobs
- itSteveJobs
- yetSteveJobs
- what a hard-on for Applehotroddy
- cmon hotroddy get over yourselfukit
- If you don't want to learn this stuff then don't, it's pretty simpleukit
- it's not personal. Much respect.hotroddy
- Then why insult? PLURukit
- good question. I'm just angry with apple.hotroddy
- ukit0
I agree, and actually the project I'm working on I decided against Canvas for that reason even though that was what the client had in mind.
excanvas got me to 90% of what I was trying to do working in IE but a couple little things were off (fonts looked kind of weird and a couple other things). If you were attempting something more complex then you'd hit an even bigger wall, but hey, at least it's coming along.
So I ended up going with SVG instead, using Rafael JS which does a much better job with IE and even supports IE6.
- ukit0
- SteveJobs0
i think one thing that holds everyone back is a committee deciding a standard. look how slowly css has evolved over the last decade.
compare that to community-based open source projects (jquery) or 3rd party companies pioneering new technologies both of which move much quicker. take a look at microsoft, who created ajax (way before it was called that) via a (ironically) built-in active-x plugin, which was later quickly natively adopted by firefox and safari using the xmlhttprequest object, and is now native in ie as well.
we've been waiting on html5 since it's inception which was waaay back in 2004. hurry it up, yo!
- The irony is we could use CANVAS, AUDIO, VIDEO, and SVG if it wasn't for IEukit
- It's not the spec that is holding that back, it's companies NOT implementing standardsukit
- no, as you even admitted above, canvas has limitations. and even if you won't admit it, it's true.SteveJobs
- LOL...wha? I said excanvas had limitations. In other words, project looked great on Chrome, Safari, FFukit
- and almost worked on IE but not quite. So that was a compatibility issue.ukit
- In terms of extending the abilities of CANVAS, I think JS is the place for that.ukit
- I mean look at what has already been accomplished with stuff like this: http://mugtug.com/da…
http://mugtug.com/sk…ukit - Or the Chrome experiments site: http://www.chromeexp…ukit
- SteveJobs0
also, i want to be optimistic about excanvas, but it's hard when the last modified date of it is March 22, 2009 :/
- ukit0
