[sweetlucipher]

The latest Safari breaks many of the WebGL demos on Shadertoy where Chrome has zero issues. I haven't investigated the reason but that could affect more than just games. TensorflowJS relies on WebGL backend for heavy model weight lifting (lots of puns)

[om2]

Could you share which specific ones? In Safari 14 we changed our WebGL to be fully based on ANGLE, and that fixed more compact issues than it caused, but there may still be some bug tail which we are trying to clean up in updates.

[sweetlucipher]

Sorry for the very late reply. Contrary to the other response which I find baffling, it’s not a WebGL2 vs WebGL1 issue. Safari 14 on Catalina was able to render 4 out of the 6 shader demos on the Shadertoy homepage on a MacBook Pro 16 2020 with AMD Radeon 5600. Chrome was able to render all. Obviously, if it was a case of WebGL version support either all would run or none would run depending on the supported version. That comment really made no sense.

Anyway, I had to return the MBP 16 as I wasn’t happy with it’s performance when the browser has to deal with multiple GPU contexts. I’m waiting for an M1 laptop and it won’t arrive till next month.

My old MBP 15 does not have Catalina so it doesn’t have the latest Safari.

Hope that helps.

[greggman3]

AFAIK Safari still has WebGL2 behind a flag which means many Shadertoy shaders will not run without enabling experimental features