4 ms·
It's easy to do this when you only need to address a single platform. Most of that overhead is probably bound to graphics layer overhead. Microsoft tightly coup
by cromwellian 12y ago
It's easy to do this when you only need to address a single platform. Most of that overhead is probably bound to graphics layer overhead. Microsoft tightly couples to DirectX. Chrome has to sit on top of SKIA to support Win/Linux/OSX/Android.
I bet Safari Canvas performance is also high, since they can directly bind to OSX.
- masklinn 12y ago> I bet Safari Canvas performance is also high, since they can directly bind to OSX. On my machine (old MBP, 10.9.5) Firefox 33: 35.2s Safari 7.1: 18.57s Chrome 34[0]: 28.6s [0] yes I know it's not up to date
- ossreality 12y ago[0]: it's not even close
- sitharus 12y agoon my 2012 rMBP running 10.10: Firefox 33: 33.255 Safari 8.0: 16.454 Chrome 38: 22.048 I should install Windows 10 tech preview underbootcamp and see how that goes.
- cromwellian 12y agoI get 12.287 secs under Safari 8/Yosemite on a Mac Pro (2014) 8-core. 15.9 secs on Chrome Canary (40.x) 20.3 secs on FF30. My guess is IE11 1) has lower OS/driver overhead and 2) accelerates more Canvas ops and does less software rendering than other platforms.
- pjmlp 12y agoThey just need to make use of respective hardware accelerated APIs in each targeted platform.
- munificent 12y agoThere are a lot of dragons hiding in that "just".