惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

L
Lohrmann on Cybersecurity
Martin Fowler
Martin Fowler
Engineering at Meta
Engineering at Meta
腾讯CDC
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Microsoft Azure Blog
Microsoft Azure Blog
G
Google Developers Blog
TaoSecurity Blog
TaoSecurity Blog
博客园_首页
Vercel News
Vercel News
Hugging Face - Blog
Hugging Face - Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Last Week in AI
Last Week in AI
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
T
The Exploit Database - CXSecurity.com
量子位
Project Zero
Project Zero
A
Arctic Wolf
小众软件
小众软件
NISL@THU
NISL@THU
C
CERT Recently Published Vulnerability Notes
有赞技术团队
有赞技术团队
MongoDB | Blog
MongoDB | Blog
博客园 - 聂微东
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
N
News and Events Feed by Topic
宝玉的分享
宝玉的分享
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Troy Hunt's Blog
P
Privacy & Cybersecurity Law Blog
Security Latest
Security Latest
B
Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
D
DataBreaches.Net
Schneier on Security
Schneier on Security
The Hacker News
The Hacker News
K
Kaspersky official blog
C
Check Point Blog
Hacker News: Ask HN
Hacker News: Ask HN
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Webroot Blog
Webroot Blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
人人都是产品经理
人人都是产品经理
AI
AI
Cisco Talos Blog
Cisco Talos Blog
MyScale Blog
MyScale Blog
Cloudbric
Cloudbric
B
Blog RSS Feed
S
Schneier on Security
P
Palo Alto Networks Blog

Henri Sivonen’s pages

Parin vuoden tutkimattomuus crates.io: Rust Package Registry Asiakirjatonta toimintaa It’s not wrong that "🤦🏼‍♂️".length == 7 Koulutartuntojen tilastointimenettely Perusteasiakirjoja hallussapitämättä ikärajoitettu Asiantuntijat ja nukkuva vallan vahtikoira Koronapassilausunto Suppealla tietopohjalla ohimeneväksi väitetty Text Encoding Menu in 2021 The Text Encoding Submenu Is Gone An HTML5 Conformance Checker Not Part of the Technology Stack Browser Technology Stack Bogo-XML Declaration Returns to Gecko A Look at Encoding Detection and Encoding Menu Telemetry from Firefox 86 Why Supporting Unlabeled UTF-8 in HTML on the Web Would Be Problematic Rust Target Names Aren’t Passed to LLVM Toimintamalli Activating Browser Modes with Doctype Johtopäätöksiä mallin rakenteesta Tehtävänmäärittelyä kirjoittamatta ja kuolemia laskematta laumasuojamallinnettu Character Encoding Menu in 2014 Erillissuosituksen tarpeettomuudesta yleissuosituksen poikkeukseksi? STM:n maskiaikajana Rust 2021 Oma-aloitteisesti mallinnettu Kokopinovaatimuksin kilpailutettu chardetng: A More Compact Character Encoding Detector for the Legacy Web Varauksia paisutellen tiedotettu Perusteasiakirjoitta tiedotettu Always Use UTF-8 & Always Label Your HTML Saying So IME Smoke Testing The Validator.nu HTML Parser About the Hiragino Fonts with CSS It’s Time to Stop Adding New Features for Non-Unicode Execution Encodings in C++ Rust 2020 The Last of the Parsing Quirks About about:blank Rust 2019 a Web-Compatible Character Encoding Library in Rust How I Wrote a Modern C++ Library in Rust Using cargo-fuzz to Transfer Code Review of Simple Safe Code to Complex Code that Uses unsafe A Rust Crate that Also Quacks Like a Modern C++ Library #Rust2018 No Namespaces in JSON, Please A Lecture about HTML5 Julkisesti luotettu varmenne ikidomainille TLS:ää (SSL:ää) varten -webkit-HTML5 Lists in Attribute Values The Sad Story of PNG Gamma “Correction” If You Want Software Freedom on Phones, You Should Work on Firefox OS, Custom Hardware and Web App Self-Hostablility HTML5 Parser Improvements ARIA in HTML5 Integration: Document Conformance (Draft, Take Two) Schema.org and Pre-Existing Communities Lowering memory requirements by replacing Schematron HTML5 Parsing in Gecko: A Build Introducing SAX Tree NVDL Support in Validator.nu HOWTO Avoid Being Called a Bozo When Producing XML An Unofficial Q&A about the Discontinuation of the XHTML2 WG Thoughts on HTML5 Becoming a W3C Recommendation Four Finnish Banks Training Users to Give Banking Credentials to Another Site Unimpressed by Leopard Sergeant Semantics The Content Sink Inheritance Diagram – 2006-06-30 What is EME? About Points and Pixels as Units The Performance Cost of the HTML Tree Builder Social Media Impression Management The spacer Element Is Gone Openmind 2006 Performance Mistake XHTML and Mobile Devices HTML5 Parser-Based View Source Syntax Highlighting Vendor Prefixes Are Hurting the Web Accept-Charset Is No More Dualroids Writing Structural Stylable Document in Mozilla Editor ISO-8859-15 on haitallinen Hourglass The Scientific Method According to Hixie Maemo Source Code Karpelan lukkovertaus ontuu Digitaalisesta arkistoinnista ARIA in HTML5 Integration: Document Conformance (Draft) XHTML—What’s the Point? (Draft, incomplete) Mac OS X Browser Comparison HOWTO Spot a Wannabe Web Standards Advocate An Idea About Intermediate Language Trees and Web UI Generation Thoughts on Using SSL/TLS Certificates as the Solution to Phishing Bureaucracy Meets the Web Europe Day HOWTO Establish a 100% Literacy Rate What to Do with All These Photos? Charmod Norm Checking Validator Web Service Interface Ideas DTDs Don’t Work on the Web EFFI’s Day in Court Speaking at XTech
WebM-Enabled Browser Usage Share Exceeds H.264-Enabled Browser Usage Share on Desktop (in StatCounter Numbers)
Henri Sivonen · 2012-09-17 · via Henri Sivonen’s pages

Looking at StatCounter stats, it occurred to me that they might not match the common narrative about H.264 market share. I decide to run some numbers using StatCounter stats. It turns out that during the first two weeks of 2012, on desktop, the usage-share of browsers that support WebM in HTML5 video exceeded the usage share of browsers that support H.264 in HTML5 video—except in North America and Oceania.

Methodology

I downloaded StatCounter data as CSV and fed it to a Python script I wrote. The script categorizes the StatCounter-reported usage share into six buckets:
  1. Total desktop (this excludes Safari on iPad, the Android browser, the browser of Playstation 3, etc.)
  2. Theora
  3. WebM
  4. H.264
  5. No support for HTML5 video
  6. Unknown HTML5 video support

The total desktop bucket adds up to 97.7% globally. In other words, the non-desktop browsers that StatCounter reports in its desktop stats account for less than 3% of usage. I divided the numbers in the other buckets by the total desktop bucket to scale the other numbers to be percentages of desktop only.

The script (which you can audit) has baked-in knowledge of which browser versions support what. Only out-of-the-box support is considered, so IE9 is considered to support H.264 but not WebM even though WebM support can be added as a separate installation. As an exception, Safari is counted as if Safari for Windows always also had QuickTime installed (because the data is not granular enough to do otherwise).

Results for Week 1 and Week 2 of 2012

The percentage means the Web usage share (as measured by StatCounter) of desktop browsers that support a given video format in HTML5 <video>. The percentages do not add up to 100%, because some browsers support multiple video formats. The numbers for Theora are always higher than the numbers for WebM, because all browsers that support WebM also support Theora but there are browsers that support Theora but not WebM.

World Africa Asia Europe North America Oceania South America
Theora 55% 64% 58% 62% 42% 49% 66%
WebM 51% 55% 52% 57% 38% 45% 62%
H.264 45% 38% 42% 44% 47% 50% 53%
No <video> 28% 27% 32% 21% 32% 25% 25%
Unknown 0% 0% 0% 0% 0% 0% 0%

Addendum: FAQ

Answers to questions from Twitter.

What Happens if You Include iPad?

I tried to make the point that the share of tablets is tiny relative to desktops. If Safari on iPad and the Android default browser are both counted as H.264 and no attempt is made to count any versions of the Android default browser as WebM (although some versions support WebM), the differences in world-wide numbers are lost in rounding and do not change the rounded percentages.

What Happens if You Include Phones?

The desktop+tablet numbers that StatCounter provides are not commeasurable with the phone numbers they provide.

What Happens if You Include Pluggable Codecs?

If pluggable codecs were considered, the WebM and Theora numbers would be higher, since IE9 supports WebM if WebM support is installed to Media Foundation and Safari (on Mac at least) supports WebM and Theora if WebM or Theora support is installed for QuickTime.

The H.264 numbers would not be higher, because Firefox and current versions of Opera do not support H.264 as a pluggable codec and Chromium usage is very low. (Earlier versions of Opera for Linux and FreeBSD supported pluggable H.264, but those versions have already faded out of significance.) The Windows Media Player extension that Wikipedia counts as adding H.264 support to Firefox does not actually add H.264 support to the HTML5 video element. Instead, it replaces the video element with a plug-in instance that does not support the HTML5 video API, so the HTML5 video element is no longer there. (Feel free to try to fix the wikitruth. I have given up.)

Can You Run the Numbers for Another Time Period?

I have no plans to do that at this time. The script is available under a Free Software license, so feel free to run it over data from a different time period.

You Are Counting Chrome as Supporting H.264 Even Though They Dropped Support!

In January 2011, they announced that H.264 support would be dropped. As of January 2012, Chrome has not yet dropped support for H.264.

Do You Count [browser] as Supporting [codec]?

Please see the source of the script.