So Apple, being the creator of the world's most advanced and the most HTML5-compliant browser engine, don't at present have enough resources to code its own site with using all HTML5 power.
Let's hope they stop misleading people into thinking Safari is the only browser that support html5, like they do at http://www.apple.com/html5/
...where the user is greeted with:
"You?ll need to download Safari to view this demo."
So the only way to appreciate this "universal standard" is to download and install one of the least-used browsers in the world. Nice message. Tells us everything we need to know.
You're joking, right? Please tell me you're joking.
What exactly is so ?jokey? about his comment? It?s made with HTML, CSS and JavaScript. What do web browsers use? What is the biggest source of advertising with those standards? If iAds take off it would be silly not to expand into an OS-independent world.
"You’ll need to download Safari to view this demo."
So the only way to appreciate this "universal standard" is to download and install one of the least-used browsers in the world. Nice message. Tells us everything we need to know.
So Apple should let Internet Explorer users try to view the demos even though they won’t work? Yeah, that makes sense…
While running that game the CPU on my MBP spiked to 98%. Gosh, I thought only Flash did that.
If you are running 10.5 or less, you'll need to upgrade to 10.6. On 10.5, I got CPU spikes but on 10.6 with Safari 4, HTML 5 stuff plays very smoothly. 30-40% CPU for that game maximum on a dual core. Safari 5 should improve things further.
Naturally you will still get content that people haven't bothered to optimise properly regardless of it being Flash or HTML 5 but what is certain is that HTML 5 content plays much smoother than Flash ever did because it's all properly hardware-accelerated and the updates come quickly.
Quote:
Originally Posted by RationalTroll
Ironically, the video on that page uses Flash.
It's not that ironic, the reality is that more people have a browser with Flash than have an HTML 5 compatible browser. Flash also has an IDE that people are familiar with for authoring content. Thanks to Adobe's grip over Internet media, we are stuck in a temporary catch-22 where content providers won't switch until enough users can see the content and users won't upgrade as long as content providers keep providing media they can watch with needing to.
Google needs to wake up and do something about legacy browsers on the most popular websites, even Google itself. All they have to do is put up a warning message saying users should upgrade to IE9 (when it arrives), Firefox, Chrome or Safari every time they try to access google.com or Youtube. Just bring up a popup that they have to dismiss every time they visit the sites using browsers below a certain level of HTML 5 support.
So Apple should let Internet Explorer users try to view the demos even though they won?t work? Yeah, that makes sense?
They should explain why it doesn't work, and let browsers that do work ...work. That way people aren't mislead into believing that Safari is the only browser that supports HTML5, or that h.264 is part of HTML5.
You don't need to use Safari to view an HTML5 demo. That's a lie.
They should explain why it doesn't work, and let browsers that do work ...work. That way people aren't mislead into believing that Safari is the only browser that supports HTML5, or that h.264 is part of HTML5.
You don't need to use Safari to view an HTML5 demo. That's a lie.
That page is for Mac developers. Those demos are specifically designed for Safari. The only other modern browser they?d probably work in is Chrome.
True. It would be nice if they made that more clear.
It would be even better if they tested for features instead of browsers. Let's hope that is the approach they take with these new HTML5 websites.
I don?t see what is so unclear about Apple pimping Safari 5. Don?t all the other browsers promote their browsers? I seem to recall IE9 pointing out how well it does with HTML5 recently with demos that are heavy in Canvas specifically because they are the only ones that support HW acceleration of Canvas.
So the only way to appreciate this "universal standard" is to download and install one of the least-used browsers in the world. Nice message. Tells us everything we need to know.
I can view the demos just fine with the latest stable Chrome version. Looks like Apple removed the browser check after the misleading message about the demos needing Safari caused a of negative feedback. Anyway, Apple was dishonest in more ways than just adding a browser check which filters out everything except Safari. They also used non-standardized webkit- prefixed CSS elements. Microsoft was intellectually more honest with their demos and used actual standards which are not tied to a particular implementation. That's why I can view most of them just fine with newer versions of the popular browsers while Apple's ones will work only on WebKit-based browsers (at best).
Comments
Let's hope they stop misleading people into thinking Safari is the only browser that support html5, like they do at http://www.apple.com/html5/
...where the user is greeted with:
"You?ll need to download Safari to view this demo."
So the only way to appreciate this "universal standard" is to download and install one of the least-used browsers in the world. Nice message. Tells us everything we need to know.
You're joking, right? Please tell me you're joking.
What exactly is so ?jokey? about his comment? It?s made with HTML, CSS and JavaScript. What do web browsers use? What is the biggest source of advertising with those standards? If iAds take off it would be silly not to expand into an OS-independent world.
...where the user is greeted with:
"You’ll need to download Safari to view this demo."
So the only way to appreciate this "universal standard" is to download and install one of the least-used browsers in the world. Nice message. Tells us everything we need to know.
So Apple should let Internet Explorer users try to view the demos even though they won’t work? Yeah, that makes sense…
While running that game the CPU on my MBP spiked to 98%. Gosh, I thought only Flash did that.
If you are running 10.5 or less, you'll need to upgrade to 10.6. On 10.5, I got CPU spikes but on 10.6 with Safari 4, HTML 5 stuff plays very smoothly. 30-40% CPU for that game maximum on a dual core. Safari 5 should improve things further.
Naturally you will still get content that people haven't bothered to optimise properly regardless of it being Flash or HTML 5 but what is certain is that HTML 5 content plays much smoother than Flash ever did because it's all properly hardware-accelerated and the updates come quickly.
Ironically, the video on that page uses Flash.
It's not that ironic, the reality is that more people have a browser with Flash than have an HTML 5 compatible browser. Flash also has an IDE that people are familiar with for authoring content. Thanks to Adobe's grip over Internet media, we are stuck in a temporary catch-22 where content providers won't switch until enough users can see the content and users won't upgrade as long as content providers keep providing media they can watch with needing to.
Google needs to wake up and do something about legacy browsers on the most popular websites, even Google itself. All they have to do is put up a warning message saying users should upgrade to IE9 (when it arrives), Firefox, Chrome or Safari every time they try to access google.com or Youtube. Just bring up a popup that they have to dismiss every time they visit the sites using browsers below a certain level of HTML 5 support.
So Apple should let Internet Explorer users try to view the demos even though they won?t work? Yeah, that makes sense?
They should explain why it doesn't work, and let browsers that do work ...work. That way people aren't mislead into believing that Safari is the only browser that supports HTML5, or that h.264 is part of HTML5.
You don't need to use Safari to view an HTML5 demo. That's a lie.
They should explain why it doesn't work, and let browsers that do work ...work. That way people aren't mislead into believing that Safari is the only browser that supports HTML5, or that h.264 is part of HTML5.
You don't need to use Safari to view an HTML5 demo. That's a lie.
That page is for Mac developers. Those demos are specifically designed for Safari. The only other modern browser they?d probably work in is Chrome.
That page is for Mac developers. Those demos are specifically designed for Safari. The only other modern browser they?d probably work in is Chrome.
So they're not HTML5 demos; they're Safari demos.
So they're not HTML5 demos; they're Safari demos.
True. It would be nice if they made that more clear.
It would be even better if they tested for features instead of browsers. Let's hope that is the approach they take with these new HTML5 websites.
True. It would be nice if they made that more clear.
It would be even better if they tested for features instead of browsers. Let's hope that is the approach they take with these new HTML5 websites.
I don?t see what is so unclear about Apple pimping Safari 5. Don?t all the other browsers promote their browsers? I seem to recall IE9 pointing out how well it does with HTML5 recently with demos that are heavy in Canvas specifically because they are the only ones that support HW acceleration of Canvas.
I don?t see what is so unclear about Apple pimping Safari 5.
Then take the time to read the post trail.
So the only way to appreciate this "universal standard" is to download and install one of the least-used browsers in the world. Nice message. Tells us everything we need to know.
I can view the demos just fine with the latest stable Chrome version. Looks like Apple removed the browser check after the misleading message about the demos needing Safari caused a of negative feedback. Anyway, Apple was dishonest in more ways than just adding a browser check which filters out everything except Safari. They also used non-standardized webkit- prefixed CSS elements. Microsoft was intellectually more honest with their demos and used actual standards which are not tied to a particular implementation. That's why I can view most of them just fine with newer versions of the popular browsers while Apple's ones will work only on WebKit-based browsers (at best).