- From: Marcos Cáceres <notifications@github.com>
- Date: Tue, 05 May 2026 17:18:11 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 6 May 2026 00:18:18 UTC
marcoscaceres left a comment (w3ctag/design-reviews#1198) Reopening for clarification on the following: 1. Why a CPU measurement, not existing targeted APIs? The motivating use cases (video conferencing, ML model selection) depend on GPUs/NPUs, not CPU. Why not extend MediaCapabilities or WebCodecs isConfigSupported() instead? Have you talked to those WGs? 2. What do apps actually do with a static number? What's the concrete application behavior? Is it "download flexible code up front"? Where's the evidence that's how apps will use it, and that it's better for users than adapting dynamically? -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1198#issuecomment-4384163029 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1198/4384163029@github.com>
Received on Wednesday, 6 May 2026 00:18:18 UTC