If I had to guess, it's that Apple refuses to implement very CPU-heavy JS features they don't think add much value in Safari.

I recall some feature I was using that ran in an inferior way to save power on Safari, so much so that I had to kill that feature and use a different API