3 ms·
Crazy talk. In 1ms, I can perspective transform a moderately big image. NodeJS cant iterate through a list. We really need a 60 fps equivalent for web stuff. Y
by revelation 12y ago
Crazy talk. In 1ms, I can perspective transform a moderately big image. NodeJS cant iterate through a list.
We really need a 60 fps equivalent for web stuff. You have 16ms, thats it.
- nostrademons 12y agoFWIW, a lot of the stuff the Chrome+Polymer team is working on explicitly has a 60fps goal and 16ms frame budgets. I remember in my last project at Google, I spent a lot of time working with the Chrome team to get various parts of websearch rendering under the 16ms budget. (I couldn't manage it given the amount of legacy code we had to work with, but various other people have continued the work since I left, so hopefully they've had more luck.)