Comments on: Firefox: The Best Worst Browser Ever!

By: camino,,

camino,, — Wed, 23 May 2007 17:35:21 +0000

i’m a fairly diehard camino user, i personally think the js rendering is quicker than in firefox (yes, i’m aware its the same engine), plus its got the look of a mac. that aside, it would be nice to see 1.1 include support for extensions… please?

By: Thoughts after trying Firefox again at D’Arcy Norman Dot Net

Thoughts after trying Firefox again at D’Arcy Norman Dot Net — Tue, 27 Dec 2005 05:30:44 +0000

[...] s suck badly, compared to the great ones that are provided by Cocoa. Apparently, I’m not the only one who feels this way. Feels like it is qui [...]

By: Steven Fisher

Steven Fisher — Sat, 17 Dec 2005 01:05:50 +0000

“I think most of the people who have posted here are missing the point behind the whole Mozilla Foundation project: CROSS-PLATFORM-COMPATIBILITY.”

I don’t think we’ve missed the point. I know I haven’t. I do, however, deny that the point has any legitimacy. I’ll put this simply: Cross platform code — good. Failing to match interfaces with the platform you’re on — bad.

By: lavelle

lavelle — Wed, 07 Dec 2005 11:17:25 +0000

I think that Firefox is the worst browser for the Windows too.

By: M.e.

M.e. — Wed, 07 Dec 2005 04:12:03 +0000

Dave - Wait until you see what I have to say about Dreamweaver tomorrow…

IE 6 Win usage is down to 46% on bottomdwellersmusic.com. 39% Firefox, 10% Safari and the remain 4% Mozilla. Life is getting better. One thing I’ve noticed since using Firefox 1.5 beta for the past few months, it and the new webkit are nearly identical.

By: dave

dave — Wed, 07 Dec 2005 04:01:02 +0000

Jesus Cripes, M.e., what the hell have you started here? I feel like i showed up to a circle jerk 10 minutes late and got handed the toast.

I prefer to use a different browser each and every day of the week. This way, I never become hater of other browsers because I never get so used to one that the loss of its features in another becomes a problem.

And I design with one browser in mind: IE 6.

By: Rich

Rich — Tue, 06 Dec 2005 12:32:59 +0000

The purpose of a browser is to let you navigate between stuff, and to read it when you’ve found it. If a browser fails, or at least is inefficient, in that purpose, then the padding between its menu items is irrelevant. Firefox achieves that purpose with an economy that Safari does not. Everything else is secondary.

I’m a (very) recent Windows switcher and proud owner of a new G4 Powerbook. Having invested heavily on the back of the hype that everything on a Mac “just works”, I fired up the Safari browser with not inconsiderable anticipation.

Imagine my disappointment when, within minutes, I couldn’t find any way of viewing my bookmarks at the same time as viewing my current choice of bookmarked location. The resulting fiasco of endlessly flipping between the two, and scrabbling around with the menu, just to flip through the news was excrutiating.

Imagine also my disappointment when Safari’s own default home page rendered in type so small I couldn’t read it, while Safari cheerfully ignored all my efforts to change the default font and size (yes, I could get round to building my own style sheet and see what happens, but why should I when I’ve a browser that does it already?).

5 minutues later, I had Firefox loaded and I could navigate and see again.

Guys - if you’re presented with a gold plated turd to eat, what matters most - the gold plating, or the turd?

By: Kees

Kees — Tue, 06 Dec 2005 07:55:04 +0000

the problem is gecko, obviously, isn’t cocoa. Since text fields and such are rendered by gecko, even in Camino, they can’t acces the system’s spell checker. Because it’s front end is cocoa, in Camino, dictionary and spellcheck does work in the google search field in the menu bar, for example (great heh
If I remember correctly, attempts were made for Camino to have it’s own text fields, but it was buggy as hell.

By: systemsboy

systemsboy — Tue, 06 Dec 2005 04:46:16 +0000

Thanks for the compliment and the info, M.e.. Liking your blog quite a bit as well.

Too bad about Camino. It’s so close to being a contender. I want to use it, but it just ain’t quite there yet.

Ah well… The wait for the perfect browser goes on…

Cheers!

By: M.e.

M.e. — Mon, 05 Dec 2005 18:34:24 +0000

kd - Thanks for the Windows browser suggestions. I knew there must have been other Windows browser alternatives available, but all I ever hear from Windows web developers is how God-like Firefox is.

systemsboy - Sorry for the moderation delay. Your Firefox conversion log is great. I wish I had read it before I wrote this post. As understand it, using the Cocoa API doesn’t automatically give you access to the system dictionary, spellcheck, or services. Programmers can use different API’s for different parts of a program. This is the biggest fault I currently find with Camino.