Hacker News Reader

Comment by darkwater | Hacker News Reader

Very cool! Now, let see how much will take for G-products to actually use it and not complaining about "browser not supported for this feature, use Chrome".

View on HN

Which google products use it?

The one I can think of is Google Meet, where some GPU-thing is used to add background effects such as blur. However I'm not sure this actually uses WebGPU; it used to use on Firefox until Google added a browser check, and AFAIK, if you could fool Meet to think Firefox was Chrome, it would still work.

This might still be a semi-legitimate thing, i.e maybe they kept around a WebGL implementation for a while as a fallback but moved the main implementation to WebGPU and don't want to maintain the fallback. It certainly fits well into their strategy of making sure that the web really only works properly with Chrome.

Official documentation suggests meet works with Firefox: https://support.google.com/meet/answer/7317473?hl=en#zippy=%...

Yeah, Meet works in Firefox, but the background effects don't.

The background effects do work, but they're using the CPU (and need a lot of it)

Huh really? That must be a relatively recent change, last time I was in a Meet meeting in Firefox I was just blocked by a message saying my browser isn't supported. That is admittedly some time ago though.

I'm on Brave Linux which requires special flag for WebGPU (not turned on for me) and can confirm that background blur still works with Meet without WebGPU

It sounds like something webgl2 should be able to handle easily.

I don't know :) I was referring basically to the Meet situation back in the day with FF where the feature was there but Meet complained the browser was not capable.

There was a genuine technical reason for that, a part of WebRTC that Firefox hadn’t implemented yet, where if even a single member of a group call lacked that feature, it had to fall back to something that used a lot more CPU for everyone. Can’t remember the details exactly, but it was approximately that.

If I remember correctly, the issue was related to newer APIs like MediaStreamTrackProcessor, offscreen surfaces, and WebRTC–WebCodecs interoperability, as well as the ability to run ML inference efficiently in the browser. At the time, Firefox hadn’t fully implemented some of these features, which impacted Google Meet’s ability to apply effects like background blur or leverage hardware-accelerated video processing.

Reply on news.ycombinator.com