It also took 6 years longer than everybody else to support WebGL2, and it’s the only browser without a working WebGPU implementation. It also has no timeline for wasm-gc, while Chrome already ships with it default enabled and Firefox will ship with it on the next release.
Apple has been removing support for garbage collection from other technologies that used to support it. Wouldn’t be surprised if they never add support for that, they’ll tell you not to waste CPU cycles (and therefore, battery power) collecting garbage.
They want you to figure out when memory should be deallocated at compile time, not run time.
It also took 6 years longer than everybody else to support WebGL2, and it’s the only browser without a working WebGPU implementation. It also has no timeline for wasm-gc, while Chrome already ships with it default enabled and Firefox will ship with it on the next release.
Apple has been removing support for garbage collection from other technologies that used to support it. Wouldn’t be surprised if they never add support for that, they’ll tell you not to waste CPU cycles (and therefore, battery power) collecting garbage.
They want you to figure out when memory should be deallocated at compile time, not run time.
I personally prefer to use such languages, but I often don’t have a choice for certain tech stacks.