3 ms·
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 syste
by plehoux 14y ago
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.
- TazeTSchnitzel 14y agoYep. Safari runs a 3D CSS demo/benchmark/unrealistic-stress-test I made much smoother than Chrome.