I am not familiar with this one. Anyway, it is very interesting because of its open nature. It's a great tool to aid the developers in exploring their creativity.

Are they making efforts to compensate for this drawback? I think they should develop something that would enable it to compress videos.

Google is a widely used site and search engine. Its integration of the Ogg in the chrome browser may change the trend because it will enable web surfers to use and appreciate the Ogg format.

If it's for free, then for sure this will happen real soon. Don't you think so?

I can assure you that it's not a computer generated article, its just that my tech skills need to be brush up a lot! I'm trying hard to ensure that I can start contributing again and that too without silly mistakes like these.

"One of the drawbacks of Ogg theora format is that it doesn’t support h.264 video compression" That's like saying one of the drawbacks of a Ford is that it isn't a Chevy. Of course it doesn't support h264. it's competing with h264.

1 – Vorbis is an audio only codec; Theora is a video only codec. They originated from totally different beginnings. Vorbis began as a grassroots effort to replace MP3 after the patent holder announced that they were going to start charging licensing fees; Theora was a video codec developed by On2 Technologies as a competitor to MPEG2 that, after it lost, granted the world a royalty-free license to do whatever they wanted with it.

2 – H.264 is a codec unto itself, not something that helps to further compress video for the web and not something that can be implemented in Theora. It's possible but highly improbable that H.264 videos could be made to play in the Ogg container. H.264 is a newer generation of video codec that uses a patently different technique to get higher quality video at lower file sizes. Theora wasn't designed to even come close to competing with H.264, and it's highly unlikely that it will ever match H.264's quality.

3 – Neither Safari nor Opera support Ogg, Vorbis, or Theora. Opera has elected to hold off supporting it right now for fear of legal threats from submarine patents, and Safari only plays Theora videos after going through the relatively user unfriendly installation of the XiphQT component.

4 – Flash supports the H.264 video codec natively. Youtube has agreements with hardware manufacturers to encode video in H.264 format because there is at present no hardware acceleration for Theora (something necessary for mobile devices and set top boxes). The same H.264 videos that Youtube will possibly serve up some day for the video tag can be used in Flash player as a fallback for older browsers. It's far more likely that Mozilla will be forced to capitulate and license a H.264 decoder in their browser than it is for Youtube to decide to support Theora.

Mozilla incorrectly implies that H.264 will be prohibitively expensive for the end user. The fact is that H.264 will in most cases incur a licensing cost for tool makers and web hosts, not an additional expense for the end user. H.264 is everywhere. OS X supports it out of the box. Windows 7 will support it out of the box. Flash supports it out of the box. It's the standard used in Bluray video. Although I am a fan of Open Source and Open Standards, I recognize that H.264 isn't going anywhere, no matter Mozilla's delusions of proselytizing against it.

In the open video codec wars to come, one can appropriately put a small amount of money on Dirac, an open, patent-unencumbered and royalty free codec developed by the BBC. Eventually, it could offer even better quality than H.264. Unlike Theora, it has a lossless mode making it suitable for everything from web video to archiving video footage. Unfortunately, at present Dirac is still extremely processor intensive, and even worse than Theora at lower, web-suitable bitrates.