●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
Become a fan of Slashdot on Facebook
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.....
byNeil ( 7455 ) writes:
Respectfully disagree - codifying existing practice and getting the browser developers to buy into incremental improvements to the status quo is what got us to HTML4 and the original CSS specs, which
I would suggest is basically the last time non-trivial improvements to the standards used to deliver
web pages saw wide-spread adoption.
In contrast, whenever the language designers have tried to forge a path without involving the people who
will write the web pages and develop the software the new standards have been largely ignored - for example: HTML3.0 and XHTML (and I write that as an XHTML fan).
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...