Mozilla can produce near-native performance on the Web

Post by jackmaney » Thu, May 30, 2013, 7:23 PM UTC

BrendanEich wrote: post #200

jackmaney wrote: post #199

Earlier quoted context omitted.

You are far from the first Mozilla employee that has responded to my complaints about Firefox, but you are the only one thus far that has been civil. In fact, just a few days ago, I was trolled on twitter by a Mozilla employee over my responses here. So, I just wanted to say thank you.

Sorry to hear about the trollery. I'm looking into it. I wonder if you have a profile that goes back years and has some property that tickles a latent bug. Sorry if I missed it: have you tried running on a brand new profile? You'll have to use the -ProfileManager option on the command line at startup, I think. /be

I'll give it a try on my home system again tonight. As for the trollery, the exchange is still visible via my Twitter profile (@jackmaney).

Post by just2n » Sun, Jun 02, 2013, 4:03 AM UTC

ux-app wrote: post #85

just2n wrote: post #65

Earlier quoted context omitted.

Like this? http://jsfiddle.net/eymAS/2/ The DOM is faster than almost everyone believes. It's not 2001 anymore, guys. Web components solve a lot of major problems, but it has little to do with DOM/CSS performance and more to do with encapsulation (ie, so your CSS/HTML/JS don't break a component). DocumentFragments and insertAdjacentHTML solved more performance problems for the DOM than most other API changes have, an…

That is very cool. I got quite bad rubber banding initially (with a reported 60fps), however after turning off v-sync in chrome://flags I got super smooth 120fps performance. Would be great if Chrome had this option off by default.

That was just caused by me not processing input properly. I've set up a proper rendering loop here and now only render the most recent mouse position on each frame:

http://jsfiddle.net/eymAS/84/

It's better, but still limited to 60fps, and since I render to the state at 0s, the worst delay we can see is ~16.6ms + rendering time.

Re: Mozilla can produce near-native performance on the Web

Re: Mozilla can produce near-native performance on the Web