●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
Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
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.
by91degrees ( 207121 ) writes:
Do we use an inferior standard or a closed standard?
Maybe "implementation dependent" is the term we're after.
byDraek ( 916851 ) writes:
Inferior standard. Judging from HTML4, by the time we could safely drop HTML5 support from our web browsers there'll be at least a dozen codecs that perform far, *far* better than H.264 does today so alleged superiority buys us very little, there'll still be a time where people interested in performance ignore the standard altogether. On the other hand, H.264's patent concerns will be with us for the next ~20 years, so Theora's advantage in ease of implementation will likely hold up for a much longer time.
bypoetmatt ( 793785 ) writes:
I wish I knew enough about this stuff to make a good guess. From a time perspective though I can see where you are going in that there will be replacements to H264 and possibly Ogg will still be around by then, at a later time of implementation.
Really, by not forcing a codec on HTML5, what does that do/what impact? I don't really understand. Can someone clarify?
bymaxume ( 22995 ) writes:
It matters very little. If Microsoft and Apple fail to implement Theora, the fact that the standard calls for it will not matter (because it will not be practical as a universal fallback).
Mozilla can't license H.264 in a way that lets downstream packagers use it, so they don't want to put it in the standard either.
The previous /. story discussing the email Hickson sent out covered this stuff pretty well.
It isn't particularly hard to do things like put a flash fallback inside of a video tag, so people that want to use the standard but still have wide reach have lots of options (flash is the de facto way to play 'web' video today, so I don't think it is unreasonable to assume that this may continue).
Parent
twitter
facebook
bydiscord5 ( 798235 ) writes:
It isn't particularly hard to do things like put a flash fallback inside of a video tag, so people that want to use the standard but still have wide reach have lots of options (flash is the de facto way to play 'web' video today, so I don't think it is unreasonable to assume that this may continue).
Then why even bother at all and let's keep on using flash. Currently as a host you only need to host a flash app and either encode your content to flv or h.264. Most of your target audience already has flash installed, and those who want to view your content will probably install flash. Since now it's undefined in the standard, that would mean that you'd have to host an h.264 for the ogg-impaired browsers, an ogg for the h.264 impaired, and then fall back to ye olde tried and tested method of the abominable
bymaxume ( 22995 ) writes:
Hence the 'people who want to use the standard'. I don't think it will improve things much tomorrow, but 5 years from now, it will probably be easier to serve video.
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
If A = B and B = C, then A = C, except where void or prohibited by law.
-- Roy Santoro
●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...