Posts tagged `Firefox`

Every so often, it’s nice to take a look at the state of Javascript performance among the various browsers. Though misleading, it’s become something of a truism that “browser performance” is just a nice euphemism for “Javascript performance,” since any website doing anything interesting is basically leveraging Javascript to do it.

What’s come up since the last time I did any sort of Javascript performance comparison? Well, Google Chrome and its JS engine (“V8″), for one. Also, something of a new era in Javascript handling that attempts to optimize how browsers handle it by converting it to bytecode (or, in the case of JavaScriptCore/Squirrelfish Extreme/Nitro, directly to native machine code). In addition, there’s been some new benchmarks arrive on the scene, which allows us to tease out bias from any particular one.

It’s amazing, really, to compare these numbers against the linked benchmark from a mere 1.5 years ago. Opera went from being the top of the heap with 9.5 to being a lazy 3rd or 4th place. And Chrome, of course, decimated the competition (so far). Read on for the testing methodology and the results.

Read more…

§3846 · June 21, 2009 · (No comments) · Tags: , , ,

GNOME logo

It’s been close to two years since I wrote GNOME Audio Player Shootout, a visual and textual comparison of some the best available audio players for the GNOME desktop.

As is usually the case in the world of free software, a lot has happened since then (and yet, in a strange way, things have stayed exactly the same). I decided to revisit some of those players and see how they’ve progressed. Some of them listed last time haven’t seen any appreciable development, and have been left off.

I realize that I am totally ignoring the daemon-based players (read: Music Player Daemon, XMMS2); this is by design, since those players open up a whole new can of worms. Suffice it to say that if you’ve decided on and XMMS2 or MPD-based player and successfully configured it, you probably don’t need any advice on choosing software.

The following programs will be covered in this review (development versions):

  • BMPx (0.40.14)
  • Rhythmbox (0.11.6)
  • Exaile (2.99.1-svn)
  • Banshee (1.4.1)
  • Quod Libet (2.0)
  • Decibel (1.00)
  • Songbird (1.0)
  • Listen (0.6~svn1044)

All of the testing was done on a fresh install (and update) of Ubuntu 8.10 in VirtualBox, using a small representative sample of my music collection (some modern, some classical, in Vorbis, MP3, and FLAC).

§2709 · December 19, 2008 · 4 comments · Tags: , , , , , , ,

Pages: 1 2 3 4 5 6 7 8 9 10


Internet Explorer

Firefox

Safari

I personally think the friendly rivalry between the open-source Webkit engine (which powers Safari, among other things) and Mozilla (the Gecko engine, actually) is one of the best things to happen to browser development in years. The constant one-upsmanship can only lead to better browsers. Well, Internet Explorer will constantly be the limiting factor, but we can dream, can’t we?

The latest thing to hit browser source repos is javascript engine improvement based on something called “trace trees”: essentially, javascript gets translated into native bytecode. The Webkit engine made the announcement a few months ago, with code codenamed “Squirrelfish,” promising massive improvements. That article’s also got a pretty good writeup.

Open Source being what it is, it was only a matter of time before Mozilla announced their own version of a trace-tree-based javascript engine. John Resig has a good writeup, as done Brendan Eich.

Read more…


Tux

About 2 years ago I wrote a piece called Five things that Desktop Linux really needs, attempting to air out my five biggest grievances with Desktop Linux. If you follow FOSS news, every year is heralded as “The Year of the Linux Desktop,” although such a thing clearly hasn’t happened yet. Now, two years later, I thought it would be interesting to revisit those five problems and see what kind of progress has been made in two years.

Read more…

§2078 · June 20, 2008 · 7 comments · Tags: , , , , , ,

I recently performed some cursory Javascript benchmarks with the new version of Firefox and Safari; curious about performance, I decided to do some testing of 32-bit browsers against their 64-bit counterparts. On Windows Vista x64, the only two browsers so available to me are Internet Explorer 7 and a recent nightly build of Firefox 3. The 64-bit comes from the Mozilla x86-64 project, specifically the build from 21 March 2008. The 32-bit build is a proper nightly from the same date from the official Mozilla FTP.

My hypothesis, before performing the tests, was that the 64-bit compilation would have little or no effect on the Javascript engine performance. It’s so difficult to optimize Javascript rendering, which is inherently single-threaded, and it seems likely to only benefit from a faster CPU clock than bigger memory registers. Afterward, I felt vindicated: Internet Explorer is likely the best test, and the difference was not statistically significant. In Firefox’s case, the 64-bit build was actually significantly worse, though this could easily be due to some other factor I have not taken into account; I have assumed that the source was compiled on the same date. See below for more details.

Read more…

§2017 · March 23, 2008 · 6 comments · Tags: , , , , ,