{
  "id": 18829811,
  "title": "A demo that never errors still never ran",
  "url": "https://urgent.news/2026/11/08/a-demo-that-never-errors-still-never-ran",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-08T01:00:43.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/prodbymarcu/a-demo-that-never-errors-still-never-ran-96"
  },
  "original_language": "en",
  "account": "The WebGPU text-to-speech runtime claimed to deliver audio in single-digit milliseconds, but a test on November 4 showed 75 seconds of silence with no error event. The browser, Chrome version 156.0.8078.79, displayed no audio nodes or error nodes. The test claimed 26x real-time performance on an iPhone, but measured 75 seconds of silence instead. The runtime checked through Apache-2.0 license, and the model weighed 43.7 MB after quantization to 8-bit integers. The demo was tested in Chrome on macOS and Windows, Safari on iOS, and Firefox on a Pixel 10 Pro.",
  "summary": "A WebGPU inference page can hand you four facts at once and none of them disagree: the UI renders, the GPU context comes back live, your click is accepted, and zero audio elements exist in the document. That was the state of my probe on November 4, against a WebGPU text-to-speech runtime advertising first audio in single-digit milliseconds, and the silence ran 75 seconds with no error event…",
  "key_points": [
    "WebGPU text-to-speech runtime claimed single-digit millisecond audio delivery.",
    "November 4 test showed 75 seconds of silence with no error event.",
    "Chrome version 156.0.8078.79 displayed no audio nodes or error nodes."
  ],
  "editors_take": "The failure of the WebGPU runtime to trigger error events during massive latency spikes suggests a critical lack of diagnostic transparency in high-performance browser-based audio implementations.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}