Firefox 4's JägerMonkey JIT status

Re:Firefox 4's JägerMonkey JIT status by adbge on Tuesday July 13, 2010 @09:36PM (#1513318)

Once this is merged into the main dev branch of Firefox, I'll build that and switch off of Chrome. The main advantage of WebKit at this point is that their JavaScript implementation is an order of magnitude faster.

Considering Chrome's GTK integration is god awful (on my box anyways), I can't wait.

[ Parent | on HN ]

Re:Firefox 4's JägerMonkey JIT status by bokbar on Wednesday July 14, 2010 @12:53AM (#1513630)

Wow, what do you do with your browser that you absolutely need to have a JS performance which is an order of magnitude better than FF 3.6? Just curious...

[ Parent | on HN ]

Re:Firefox 4's JägerMonkey JIT status by tsuraan on Wednesday July 14, 2010 @10:03AM (#1514564)

High performance isn't just about getting stuff done faster, it can also be thought of as getting the same amount done in less CPU time. When I'm running on batteries, my laptop's CPUs are running at 800MHz, and I get about 8-10 hours of battery life. If something's making my computer work, my CPUs go up to 2.4GHz, and my battery life plummets. More efficient javascript engines should be able to do the same work with less battery use, which makes me happy.

[ Parent | on HN ]

Re:Firefox 4's JägerMonkey JIT status by GeneralMaximus on Wednesday July 14, 2010 @07:35AM (#1514262)

  1. Facebook
  2. Google Wave
  3. Google Docs
  4. And a bunch of other webapps I'm forgetting ...

Try out Wave on an older version of Firefox (say, 3.0 or even something from the 2.x branch if you're adventurous). It totally destroys the browser.

[ Parent | on HN ]

Re:Firefox 4's JägerMonkey JIT status by Perceval on Wednesday July 14, 2010 @11:23AM (#1514838)

http://www.folklore.org/StoryView.py?project=Macintosh&s...

"Well, let's say you can shave 10 seconds off of the boot time. Multiply that by five million users and thats 50 million seconds, every single day. Over a year, that's probably dozens of lifetimes. So if you make it boot ten seconds faster, you've saved a dozen lives. That's really worth it, don't you think?"

Those few seconds add up.

[ Parent | on HN ]

Re:Firefox 4's JägerMonkey JIT status by lispygem on Wednesday July 14, 2010 @12:56AM (#1513638)

What's up with downvoting? It's a great question, I'm intrigued by adbge performance requirements as well.

[ Parent | on HN ]

Re:Firefox 4's JägerMonkey JIT status by thaumaturgy on Tuesday July 13, 2010 @11:05PM (#1513474)

Firefox 4 still has a little ways to go (of course). I've been running the beta since it came out.

I accidentally discovered a neat DoS in Firefox 4 while working on some JS: the alert loop from hell is persistent even after you close the tab. IIRC, in 3 it was possible to close the tab in between alert()s and they would go away; in 4, you'll have to kill and restart Firefox to get rid of them. Chrome still has an advantage there.

[ Parent | on HN ]

Re:Firefox 4's JägerMonkey JIT status by modeless on Tuesday July 13, 2010 @11:11PM (#1513483)

They're working on fixing this the Right Way and right now it's on the list for Firefox 4: https://bugzilla.mozilla.org/show_bug.cgi?id=562258

[ Parent | on HN ]