9 Mac Browser Shootout

I didn't know there were precisely 9 browsers available for the Mac, but I did know there were probably 7 or more. Ars Technica does a 9 Mac Browser Shootout comparing all nine in speed, rendering quality, features, and how well they fit as Mac browsers, or horrible indy ports (like Mozilla, Firebird ;). Naturally, Safari ranks high, but there is still plenty of room between version 1.0 and 2.0, with speed tweaks, revised features, increasing standards compliance, and the opening up of its WebCore code to the FSF-compliant APSL 2.0 license.

On the topic of FSF-compliant but not GPL-compliance, the FSF has given Apple the FSF seal of approval, but still insists that APSL 2.0 is not GPL compatible, and insists a company should not be judged by part of its software portfolio, but all. Do you agree? Disagee? Why?

I wonder if Apple is actually moving to full GPL certification, and will open up OSX. How about tossing out Darwin in favour of the Linux kernel, good idea?

Comments

I'll be pedantic and point out that

as every BSoD tells us, NT/2K/XP are fundamentally microkernel OSs. Although purists say otherwise.

The NT Kernel is great

It's what's on top that doesn't work so well :wink:

Firebird

Mr. gfair seems to say that Firebird is horribly indy port. I think, Mr. gfair, that firebird is not a horribly indy port. I use firebird on my PC and it is a rocket!

The Interface, not the code.

There seems to be a rather large disparity between your response, and what I said. I can see how easy it would be for you to assume I was referring to speed, because after all, raw computational performance is the God of computer cultists. But neither I, nor the reviewer, was talking about speed, we were talking about the qualitative assessment of the "fit" of the application. And I quote:

"Ars rounded up the contenders, threw a few web pages at them, and took note of the results. In this browser smackdown, we wanted to look at three aspects of the browsing experience: user experience, compatibility, and speed. First, how is the interface? Does it fit well with the OS X GUI? Does it feel like a port?"

"The applications reviewed can be grouped into 3 types based on their rendering engines: Gecko, WebCore, or proprietary."

Note: I consider proprietary to mean an independent effort, and I've been abbreviating "independent" to "indy" lately, in line with the lingo of music-savvy people, and it is one-and-the-same with software. Hence, an "indy" port.

"Firebird
Cons:
*Non Mac-like interface"

"Mozilla, Mozilla Firebird, and Netscape are all rock solid, stable, and standards-compliant. My biggest complaint about them is that they do not feel like OS X applications; rather, they feel like ports."

Mac users, gauravrampal, you either know or may learn can be highly qualitative, it is a behaviour almost central to the Mac-user culture. We compare all things to how Apple does them, and thus this is why qualitative assessment was included in the review at all - because it is extremely relevant to Mac users at least on some level. And that is why I call Firebird a horrible indy port. I've never seen the program in my life, but I know precisely what the writer is speaking of, having seen Safari, IE, OmniWeb, Opera, Mozilla, Camino and almost all of the web browsers reviewed. It doesn't look at all like it was written by Apple, and thus we will tolerate it for its performance, and use it, but it is also why a quantitatively inferior browser like Safari, which is vastly superior in qualitative measurements, will dominate while Camino plays the bit-part. It never did make sense that the Mac Mozilla developers never Apple-fied the Mozilla GUI. What are they thinking?

Firebird

I see what you mean. I have not seen the firebird port on a mac, but it is a pleasure to use on a PC.
On the Mac I use a Safari, as it is integrated into my .mac account.

Oops! Mixing metaphors

Graham -- "proprietary" does not equal "independent" -- and I have also never heard "indy" used in reference to any software development. I knew what you meant, so I just ignored those parts.

As well, Mozilla and Firebird both use Gecko.

They are both ports, done in the usual manner by open source volunteers (in this case, under the aegis of the Mozilla Foundation).

Eliminating Possibilities

Hmm... to begin to compare things to "How Apple Would Do Them" seems to be a bit short-sighted. Are you saying that Apple has developed the world's best user-interface and no one else will ever be able to make improvements?

More like

Ha. Imagine this, Dave: you have a set of playing cards. All the images, the back, etc. all look similar -- they fit together as a pack. Then imagine inserting a card with a green back and extra-large fonts. Oh, and they use different abbreviations, so an ace is denoted by a "C" instead of an "A".

Apple has Human Interface Guidelines ("guidelines" -- you can break them whenever you want, but it's likely that you better have a good reason).

Since Mozilla/Firebird use their own logic (different keyboard shortcuts, their own preferences widget instead of the standard Apple preferences dialog, etc.) it makes them appear really jarring next to "native" applications.

Imagine if an application changed Ctl-C/V/X to do something else other than copy/paste/cut.

Most of these concepts seem quite strange to long-time Windows users, because it's quite possible that every application functions in different ways and has a different look.

Fair enough...

But, it would just make me :sick: (sick - had to use that smiley) to my stomach to think that Apple had the final solution... :)

No GUI compliance on OS X

Gaurav -- Firebird is great on the PC. On the Mac, both it and Mozilla use their own UI completely (for the most part), ignoring "native" look-and-feel of OS X.

So, to the average Mac user, who is used to having a high level of consistency amongst all apps, the browsers stick out like sore thumbs.

Darwin is good

They say that micro-kernels are supposed to be much more secure than monolithic OSes; and they hide the complexity of multi-processor systems from high level processes.

Learn more about microkernels

Very true. I found a good link to Darwin and Mach microkernel that is worth reading.

Nope

Much like the author of the article, I pretty much exclusively use Safari, with Camino as my fallback for some rare sites.

I wonder if Apple is actually moving to full GPL certification, and will open up OSX.
I doubt Apple will move to "full GPL certification". Mainly because there is no such thing. Many systems ship with software that has a mix of licenses -- most notably, it tends to be BSD and GPL. As a business, Apple will continue to open-source those parts of its software where it makes business sense to do so.

How about tossing out Darwin in favour of the Linux kernel, good idea?
Darwin is the name for the BSD sub-layer, which is a bunch of software that includes the kernel, which is Mach 3.

Linux software increasingly runs on Darwin with nothing more than a re-compile, especially as more libraries get ported. Abandoning/switching out Darwin is just not going to happen.

Full GPL-certification

Full GPL-certification is a phrase that needs no quotes around it, seeing as how the APSL was once Open Source certified, and now Free Software certified, this act of license review and certification is a formal business activity of the FSF and the OSI, it isn't some particular phrase I created.

As for the definition of Darwin, it's good you pointed that out Boris, just in case someone doesn't know what it is.

But there are many advantages to adopting Linux, including (from here on out, when I say "Linux", I am referring specifically to the monolithic Linux kernel):

- Linux is a standard, broadly used and accepted, and Apple is supposedly playing the good samaritin by adopting as many standards as possible. Apple would be doing well for its customers, specifically enterprise customers buying XServe, by adopting the Linux kernel, which is far more accepted (as well as the entire Linux OS) in IT than Darwin/OSX.

- Apple develops and maintains Darwin, volunteers develop and maintain Linux. Hence, all that development and maintenance could be outsourced, and contributed to, rather than entirely repeated in-house. When it comes to OS kernels, they do not have the same economics as an OS, or a CPU, to an independent, integrated computer company like Apple that needs differentiation to maintain competitive advantage and core competencies that make it a worthwhile ongoing concern. Mach was also made with the idea of portability, including kernel portability that it may be replaced, and indeed it has. There are some four or five versions of Mach, some entirely different, that can be interchanged with fair ease because the kernel is portable as well as everything on top of it.

Those two advantages, alone, are enough in my mind to seriously consider adopting Linux. And by opening up OSX, Apple has a way to undermine Windows in a way that co-operates with Linux, they gain a lot, and in return they can return a lot more than just OSF or FSF-certified operating system software pieces.

Darwin is BSD

you make it sound like Darwin was some kind of proprietary operating system. Your argument would make sense if we were talking about the old legacy Mac OS, but they don't make sense when talking about BSD.