●Stories
●Firehose
●All
●Popular
●Polls
●Software
●Thought Leadership
Submit
●
Login
●or
●
Sign up
●Topics:
●Devices
●Build
●Entertainment
●Technology
●Open Source
●Science
●YRO
●Follow us:
●RSS
●Facebook
●LinkedIn
●Twitter
●
Youtube
●
Mastodon
●Bluesky
Follow Slashdot blog updates by subscribing to our blog RSS feed
Forgot your password?
Close
This discussion has been archived.
No new comments can be posted.
Load All Comments
Full
Abbreviated
Hidden
/Sea
Score:
5
4
3
2
1
0
-1
More
Login
Forgot your password?
Close
Close
Log In/Create an Account
●
All
●
Insightful
●
Informative
●
Interesting
●
Funny
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
by_Hiro_ ( 151911 ) writes:
It seems like Apple has something against implementing any Xiph codec... FLAC and Vorbis support in iTunes is nonexistent, and even with the QuickTime plugin, iTunes still doesn't have proper tagging support. And now refusing to add Theora support in Safari?
Perhaps someone on the Xiph board did something to one of Apple's Media guys when they were kids or something?
byAnonymous Coward writes:
Regardless of why they have some hatred for Xiph who cares what Apple's doing? Just specify Ogg. Apple will either lose market share as people switch to a browser that doesn't suck or they'll cave and use Ogg. If you can get 3 of them to agree I'd say that's pretty good. Are we just going to stop bothering to innovate because Apple won't give us its blessing? Let's just rename Apple to "Microsoft" and call it a day.
We (developers) are the ones that determine who wins the browser battles. We make the sites
byshutdown -p now ( 807394 ) writes:
You misunderstand the nature of HTML5 standardization process. Unlike previous HTML iterations, which were designed by W3C committee which largely did not intersect with people who actually implemented it, HTML5 is a vendor-driven effort that had only recently came under the aegis of W3C (after the latter's XHTML 2.0 died a quick and painless death). Since it's vendor-driven, it's going to be exactly what the vendors can agree upon - no more, and no less.
bymortonda ( 5175 ) writes:
Since it's vendor-driven, it's going to be exactly what the vendors can agree upon - no more, and no less.
That sounds pretty worthless.....
byshutdown -p now ( 807394 ) writes:
That sounds pretty worthless.
Does it? Have you actually seen the HTML5 draft spec? There's a lot of new stuff there even with all the constraints - <canvas> is a good example of one very powerful new feature; and there are plenty more.
byjez9999 ( 618189 ) writes:
Does it? Have you actually seen the HTML5 draft spec? There's a lot of new stuff there even with all the constraints - <canvas> is a good example of one very powerful new feature; and there are plenty more.
Is that the one that Microsoft aren't implementing?
byshutdown -p now ( 807394 ) writes:
There hasn't been a "yes", but there hasn't been a "no" either (and IE9 wasn't even announced yet). In truth, we do not know. IE8 implements a few chosen bits off HTML5, so there may be more to come.
Parent
twitter
facebook
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
Slashdot
●
●
Submit Story
It is much harder to find a job than to keep one.
●FAQ
●Story Archive
●Hall of Fame
●Advertising
●Terms
●Privacy Statement
●About
●Feedback
●Mobile View
●Blog
Do Not Sell or Share My Personal Information
Copyright © 2026 Slashdot Media. All Rights Reserved.
×
Close
Working...
Working...