Revisiting Linux Part 1: A Look at Ubuntu 8.04
by Ryan Smith on August 26, 2009 12:00 AM EST- Posted in
- Linux
Applications: Web Browsing
Windows Default: Internet Explorer 7
What I use: Firefox 3
Ubuntu Default: Firefox 3
Much to the chagrin of Microsoft, the web browser is turning in to a miniature OS of its own, and in the case of anything that’s not Internet Explorer, it’s a miniature OS that has no allegiance to a real operating system. It’s the primary way to retrieve most information from the internet, applications can be created through AJAX and Flash, video can be watched (see: Hulu). A good cross-platform web browser removes a great deal of the need to use any specific OS, and this is something that works in Ubuntu’s favor.
Ubuntu ships with Firefox 3, Internet Explorer’s loyal opposition and currently the #2 browser on the market. So long as a site isn’t built for IE6 Firefox has great compatibility, good speed, and an army of extensions to add features to it. Since many of you already use it, there’s not a lot to say here: it’s a very solid browser, and something I find to be superior to Internet Explorer.
As I already use Firefox under Windows, the transition here was virtually non-existent. Ubuntu doesn’t have any direct Windows to Ubuntu transition tools, but after moving my Firefox profile from Windows to Ubuntu and reconfiguring a few location-sensitive settings, I was up and going. Internet Explorer users are going to have more of a transition obviously, but it’s not much. All of the major browsers’ core behaviors are the same, which makes it easy to switch among them with little fuss.
At the risk of marginalizing the rest of Ubuntu, I consider Firefox to be one of the core components that makes Ubuntu a success story. Because so much computer use these days is inside a browser, it has become a lynchpin for a good OS. If your browser is bad, then it’s probably hurting the usability of your OS if it means that many users cannot do something they regularly do on another browser. One only needs to look at the early versions of Mac OS X to get a good picture of this, as it shipped with the only-bearable Internet Explorer 5.
There are however a few caveats that I’d like to hit on. Something that continues to throw me for a loop is that while it’s the same Firefox I use under Windows and Mac OS X, it doesn’t necessarily look the same. The rendering engine is the same, but OS differences start to play out here. Mac OS X, Windows, and Ubuntu all render text slightly differently, and in the case of Ubuntu come with a significantly different font set. Because Firefox is at the mercy of the OS for fonts, what you get are small but noticeable differences in how the same page looks.
Firefox with default fonts
Firefox with MS Core fonts
Firefox under Windows
Above we have AnandTech rendered in Firefox 3 on Windows, and Ubuntu. On Windows Firefox uses Times New Roman and Arial for its default fonts, but these fonts do not exist on Ubuntu; rather Ubuntu uses what’s called “serif” and “sans-serif”. This along with how the two OSs differ in font anti-aliasing results in the different look of Firefox under Ubuntu. Having used Windows for a number of years, I have never gotten past the idea of Ubuntu looking “wrong” even though the right look is entirely subjective.
Ultimately I ended up adding the missing fonts by installing the msttcorefonts package, which contains Times New Roman, Arial, and the other “big name” standard fonts. With those installed and Firefox configured to use them, text looks much closer, although not quite the same. It’s a shame that Ubuntu can’t include these fonts by default.
The second caveat is one of performance. When using Javascript-heavy sites in particular, Firefox on Ubuntu seems just a bit slower than under Windows. I had never been able to figure out why until I saw this Slashdot article. Firefox for Linux is not compiled with profile guided optimization, a method of improving the performance of binaries by looking at how they’re used. While Ubuntu compiles their own releases of Firefox, they do the same thing. As a result, there’s a speed difference in Firefox – it’s the same code, but the Windows version is compiled in such a way that it’s faster. As I wrote at the start of this article, I’m not concerned with the performance of Ubuntu or its applications for the most part, and this falls under that notion. Firefox is slower, but not to the point that I care. It’s interesting enough that it bears mentioning, however.
Just to give you an idea of what the speed difference is, here’s a breakout of one of our Firefox benchmarks from the benchmarking section later in this article:
As you can see, in this Javascript-heavy test Firefox on Ubuntu is upwards of 17% slower than it is under Windows. As this performance gap manifests itself largely under Javascript-heavy situations; regular browsing doesn’t show nearly the difference. Flash is also slower, but this has nothing to do with Firefox and more to do with Flash’s mediocre performance under any OS that isn’t Windows.
The last caveat is one of how Ubuntu’s distribution model becomes strained when it comes to Firefox. Ubuntu Hardy shipped nearly 2 months before Firefox 3 did. But because Ubuntu is meant to be a stable platform they still needed to package Firefox 3 with the OS, so Firefox 3 Beta 5 was included. If we had done this article a month after Hardy launched as intended, I’d have few nice things to say. Firefox 3 Beta 5 combined with Adobe Flash 9 was buggy, unstable junk. Canonical made the right decision as the final version of Firefox 3 turned out well, but it highlights the pitfalls of including 3rd party software with the OS.
The flip side of this caveat is that Firefox 3.5.x has superseded 3.0.x as the newest Firefox branch, which means that only 3.0.x versions are being pushed out to Hardy. This means if you want to take advantage of any of Firefox’s newest features such as the new javascript engine, you’ll need to install a 3.5.x build separately, ideally through a PPA package so that it cleanly replaces the default version of Firefox.
But even with those caveats, none of them are serious issues. Firefox 3 is still a fantastic browser and there’s nothing else I’d rather have on Ubuntu.
Final Verdict: Meets My Needs
195 Comments
View All Comments
jasperjones - Wednesday, August 26, 2009 - link
I second most of Fox5's suggestion.1.) I've been completely ignorant of software development on Windows over the last few years. Comparison of MS Visual Studio vs Eclipse or vs Netbeans/Sun Studio? How fast are CLI C++ apps on Windows vs. Linux? Perhaps using both GNU and Intel C++ Compiler toolchains on Linux. And possibly MS Visual C++ and Intel Visual C++ on Windows.
Perhaps less esoteric, 2.) instead of benching SMB/CIFS on Windows vs Samba on *nix, bench something *nix native such as scp/sftp or nfs. Netperf.
3.) Number-crunching stuff. I guess this is sort of similar to running at least a few synthetic benches. LINPACK or some other test that uses BLAS or LAPACK, tests that use FFTW. Maybe even SPEC (I wouldn't expect any exciting results here, though, or are there?)
Eeqmcsq - Wednesday, August 26, 2009 - link
Are you looking for benchmarks in Windows vs Ubuntu with the same hardware? Or benchmarks in different CPUs/motherboards/etc with the same Ubuntu?Ryan Smith - Wednesday, August 26, 2009 - link
Cross-platform. There's no problem coming up with Linux-only benchmarks for hardware.Eeqmcsq - Wednesday, August 26, 2009 - link
I have a question about your benchmarks that involve files, such as copying and zipping. When you run your benchmarks, do you run them multiple times and then get an average? I ask that because I have learned that in Linux, files get cached into memory, so subsequent runs will appear faster. I suspect the same thing happens in Windows. Do you take that into account by clearing cached memory before each run?Ryan Smith - Wednesday, August 26, 2009 - link
We reboot between runs to avoid cache issues (and in the case of Windows, wait for it to finish filling the SuperFetch cache).fri2219 - Wednesday, August 26, 2009 - link
I heard Sony is coming out with this thing they call a Walkman.You should review that next!
StuckMojo - Wednesday, August 26, 2009 - link
ROFL!Fox5 - Wednesday, August 26, 2009 - link
The LTS is really for the same types of people that avoid grabbing the latest MS service pack. IE, anyone who's still running Windows XP SP2 with IE6. Do that comparison and see how they compare.Ubuntu is little more than a tight integration of many well-tested packages, there's no reason to go with ubuntu's LTS when everything else already goes through it's own extensive testing. Given how quickly open source software advances, I'd say the LTS is probably less stable than the most up to date versions, and certainly far behind on usability.
You want the equivalent of Ubuntu's LTS in Windows? It most closely matches the progression that the Windows server versions follow.
Ryan Smith - Wednesday, August 26, 2009 - link
To put things in perspective, 8.04 was released shortly after Vista SP1 and XP SP3 were. So Hardy vs. XP SP2 (a 4 year old SP) is a pretty poor comparison.You'll see an up to date comparison in part 2 when we look at 9.04.
awaken688 - Wednesday, August 26, 2009 - link
I'm glad you did this article. It really has been something I think about. I'm ready to read your Part II. As others have mentioned, I have a couple of other articles that would be great.1) The comparison of the various versions as mentioned. SuSe, Ubuntu 9.04, BSD, etc...
2) Someone mentioned VirtualBox. I'd love to hear more about this including a detailed setup for the normal user. I'd love to be able to surf while in Linux, but able to play games in Windows and keep them separate for added security.
Thanks for the article! Hope to see one or both of the ideas mentioned above covered.