HTML 5 Will Leave Video in the Air
HTML 5 — the next generation of the language that defines the World Wide Web — has made great strides in the way browsers handle media. Rather than utilizing proprietary technologies like Flash or Silverlight, HTML 5 will implement audio and video tags that provide multimedia content outside the existing frameworks. For all its progress, however, it's now known that what the specification won't have is a standard video codec.
The issue of which codec would become the standard for the specification — a matter now rendered moot — has been hotly contested. The Open Source Ogg Theora codec had been slated to take the title, a victory not just for improving the web experience, but also for open standards. That victory has been delayed — if it comes at all — due to the usual delaying factor: the vendors.
Ian Hickson, maintainer of the HTML 5 specification, announced last week that the plan to include Ogg Theora in the specification as the standard video plugin would be scrapped due to opposition from browsermakers. Both of the plugins being considered — H.264 being the other — are apparently vehemently opposed by varying sides of the browser wars. According to Hickson, Apple refuses to include Theora because of a "lack of hardware support and an uncertain patent landscape."1 Mozilla's Firefox 3 includes Theora support, but will not implement H.264 because of patent and license concerns, a position shared by the makers of the Opera browser.
Google's Chrome has support for both codecs, though the Linux version — Chromium — does not include H.264 for licensing reasons, and the company has expressed concern that Theora is not yet ready for use in high-volume media situation, such as its own YouTube. Microsoft, which holds a majority but steadily dwindling share of the browser market with its Internet Explorer offering, apparently has nothing nice to say, because its said nothing at all.
The result of this corporate version of "I'll take my toys and go home" is that Hickson's only option to dodge a zugzwang is to do absolutely nothing, which is exactly what he plans to do. "I have therefore removed the two subsections in the HTML 5 spec in which codecs would have been required, and have instead left the matter undefined, as has in the past been done with other features like IMG and image formats, embed and plugin APIs, or Web fonts and font formats." He went on to paint two scenarios: Either Theora will gain sufficient share to quiet Apple's fit and thus become the de facto standard, or the patents on H.264 that give all the others the heebie-jeebies will expire and it will become the de facto standard.
One way or another, Hickson says the issue will be revisited, possibly taking the search for an audio standard as a guide: "Since audio has a much lower profile than video, I propose to observe the audio feature and see if any common codecs surface, instead of specifically requiring any. I will revisit this particular topic in the future when common codecs emerge."
The situation is as it is, but that isn't to say Hickson is in the least bit pleased about it. "This is a terrible situation for the spec to be in. I wish we had good answers instead of this quagmirish deadlock."
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Returning Values from Bash Functions
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide