Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My guess is that Safari rendering system use hardware acceleration and Chrome doesn't.

The bottleneck here is not javascript, it is the browser rendering system when applying all those css 2d transform.



Yep. Safari runs a 3D CSS demo/benchmark/unrealistic-stress-test I made much smoother than Chrome.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: