3 ms·

I'm surprised to hear that. My apps all use relatively simple js, so I have no experience one way or the other personally. But I'm curious to hear what these "o

I'm surprised to hear that. My apps all use relatively simple js, so I have no experience one way or the other personally. But I'm curious to hear what these "other constraints" are?

gruseom 18y ago
Rendering and DOM. For example, setting the position and size of a div. The difference is dramatic: Webkit is probably an order of magnitude faster than Gecko right now. And as far as I can tell, JS has nothing to do with it. (In fact the most intensive JS code we have runs slower in V8 than in IE7, which is bizarre, but doesn't matter because it's no bottleneck.)
- bootload 18y ago
  "... Webkit is probably an order of magnitude faster than Gecko right now. And as far as I can tell, JS has nothing to do with it ..." This is where a cross-browser test suite could be handy checking which api you call against different browsers. Have you looked at http://ejohn.org/projects/dromaeo-javascript-performance-testing/ http://ejohn.org/projects/dromaeo-javascript-performance-tes... then ( http://wiki.mozilla.org/Dromaeo http://wiki.mozilla.org/Dromaeo ) and http://dromaeo.com/ http://dromaeo.com/ to see the real difference b/w browsers?
  - gruseom 18y ago
    Well, the real difference between browsers that I care about is how well they run my app! However, I'm not sure I'm understand your point. How would those test suites help?
    - bootload 18y ago
      "... The slowdown is in the DOM ... setting the size and position of (absolute) divs, and setting their text content ..." Run the tests (set size, position of divs, set text content) in the testing app, check the numbers returned to see how each DOM operation effects different browsers. The test app allows for DOM selection, modification or attributes for example. You can run these tests against various browsers (Firefox 2+, Safari 3+, and Opera 9+, and Internet Explorer 6+). You could use this to test which browser is slow for particular DOM operations ~ https://wiki.mozilla.org/Dromaeo#Running_the_Tests https://wiki.mozilla.org/Dromaeo#Running_the_Tests and possibly isolate where. Of course I didn't ask if you are doing this as raw Javascript or using a library? Are you using JQuery, Prototype, DOJO?

I'm surprised to hear that. My apps all use relatively simple js, so I have no experience one way or the other personally. But I'm curious to hear what these "other constraints" are?

gruseom 18y ago

Rendering and DOM. For example, setting the position and size of a div. The difference is dramatic: Webkit is probably an order of magnitude faster than Gecko right now. And as far as I can tell, JS has nothing to do with it. (In fact the most intensive JS code we have runs slower in V8 than in IE7, which is bizarre, but doesn't matter because it's no bottleneck.)

bootload 18y ago
"... Webkit is probably an order of magnitude faster than Gecko right now. And as far as I can tell, JS has nothing to do with it ..." This is where a cross-browser test suite could be handy checking which api you call against different browsers. Have you looked at http://ejohn.org/projects/dromaeo-javascript-performance-testing/ http://ejohn.org/projects/dromaeo-javascript-performance-tes... then ( http://wiki.mozilla.org/Dromaeo http://wiki.mozilla.org/Dromaeo ) and http://dromaeo.com/ http://dromaeo.com/ to see the real difference b/w browsers?
- gruseom 18y ago
  Well, the real difference between browsers that I care about is how well they run my app! However, I'm not sure I'm understand your point. How would those test suites help?
  - bootload 18y ago
    "... The slowdown is in the DOM ... setting the size and position of (absolute) divs, and setting their text content ..." Run the tests (set size, position of divs, set text content) in the testing app, check the numbers returned to see how each DOM operation effects different browsers. The test app allows for DOM selection, modification or attributes for example. You can run these tests against various browsers (Firefox 2+, Safari 3+, and Opera 9+, and Internet Explorer 6+). You could use this to test which browser is slow for particular DOM operations ~ https://wiki.mozilla.org/Dromaeo#Running_the_Tests https://wiki.mozilla.org/Dromaeo#Running_the_Tests and possibly isolate where. Of course I didn't ask if you are doing this as raw Javascript or using a library? Are you using JQuery, Prototype, DOJO?