3 ms·

WebGL took forever on mobile. WebGPU still is only partially supported on desktop. Memory64 isn't available yet at all. That's just my short list of things I c

WebGL took forever on mobile. WebGPU still is only partially supported on desktop. Memory64 isn't available yet at all. That's just my short list of things I care about, but any time I look at the boxes in caniuse safari is always the red one.

troupo 1y ago
> WebGL took forever on mobile. Since 2014, three years after desktop, I'll grant you that (though it's not forever) > WebGPU still is only partially supported on desktop. And it's only partially supported in Firefox. Perhaps something to do with actually fleshing out the APIs and not rushing with implementations like Chrome? Edit: Firefox enabled WebGPU only on Windows this year. Safari enabled WebGPU on all devices this year with *OS 26. > Memory64 isn't available yet at all. You mean the one released in Chrome this past February, and in Firefox this past January? Less than a year old? And used on a whopping 0.0001% pages? https://chromestatus.com/metrics/webfeature/timeline/popularity/366 https://chromestatus.com/metrics/webfeature/timeline/popular...
- overgard 1y ago
  These things sit in standards comities for years. Firefox has way fewer resources than everyone else, but Safari has no excuse other than that they mostly can't be bothered, because they'd rather you use an app. And honestly I wouldn't care except they don't let you USE ANY OTHER ENGINE in mobile. If I could just skip Safari I would, but even Chrome on iOS is basically Safari.
  - troupo 1y ago
    > These things sit in standards comities for years. Often for s good reason. Once something is in a browser, there's signs no change in hell to fix it or remove it. Chrome doesn't care. They just ship whatever even if the other vendors are actively against it for many reasons.