You're not wrong (I develop that way as well), but I'd wager that like me you're not neck deep in service workers and WASM and a "compression streams API." Thi

You're not wrong (I develop that way as well), but I'd wager that like me you're not neck deep in service workers and WASM and a "compression streams API." This isn't a Chrome vs Safari issue (Safari is better, of course), it's the fact that browser development suffers from Apple's corporate wall of silence. In this case, devs literally suffering.