Comments on: QotD: Firefox http://nslog.com/2004/11/10/qotd_firefox The Weblog of Erik J. Barzeski Wed, 23 May 2012 23:05:21 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: MacUser http://nslog.com/2004/11/10/qotd_firefox#comment-12461 MacUser Fri, 03 Dec 2004 11:45:33 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12461 I also use Safari only on my Mac , but , as said above some pages don't show up well in Safari , so , Camino to the rescue , but it doesn't work always , strangely , Omniweb does while it uses the same engine as Safari So OmniWeb to the rescue it is I also use Safari only on my Mac ,

but ,

as said above some pages don't show up well in Safari ,

so ,

Camino to the rescue ,

but it doesn't work always ,

strangely ,

Omniweb does while it uses the same engine as Safari

So OmniWeb to the rescue it is

]]> By: raoli.com http://nslog.com/2004/11/10/qotd_firefox#comment-12462 raoli.com Fri, 12 Nov 2004 06:21:30 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12462 <strong>Firefox 1.0</strong> In his Question of Two Days Ago, Erik Barzeski asked if we, the readers, care about Firefox. My answer is Yes. 95%+ of the time I’m browsing the Web, I’m using Safari or some other WebKit-derived browsing interface. However, there... Firefox 1.0

In his Question of Two Days Ago, Erik Barzeski asked if we, the readers, care about Firefox. My answer is Yes. 95%+ of the time I’m browsing the Web, I’m using Safari or some other WebKit-derived browsing interface. However, there...

]]> By: Tim Buchheim http://nslog.com/2004/11/10/qotd_firefox#comment-12460 Tim Buchheim Thu, 11 Nov 2004 19:34:44 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12460 I only use Firefox on non-Mac platforms. On Mac OS X I nearly always use Safari, but I keep a copy of Camino around for pages which don't work for whatever reason in Safari. (This is very rare.) I only use Firefox on non-Mac platforms.

On Mac OS X I nearly always use Safari, but I keep a copy of Camino around for pages which don't work for whatever reason in Safari. (This is very rare.)

]]> By: Troy Brumley http://nslog.com/2004/11/10/qotd_firefox#comment-12459 Troy Brumley Thu, 11 Nov 2004 13:18:39 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12459 Yes, I do. In a word--extensions. If Safari had similar capabilities, I'd use it full time. Yes, I do. In a word--extensions. If Safari had similar capabilities, I'd use it full time.

]]> By: Ralph Scheuer http://nslog.com/2004/11/10/qotd_firefox#comment-12458 Ralph Scheuer Thu, 11 Nov 2004 10:18:51 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12458 I certainly meant "cache" not "cash" (morning language barrier, I think ;-) I certainly meant "cache" not "cash" (morning language barrier, I think ;-)

]]> By: thomas@terminaljunkie.com http://nslog.com/2004/11/10/qotd_firefox#comment-12457 thomas@terminaljunkie.com Thu, 11 Nov 2004 09:07:24 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12457 I have tried both Safari and Firefox but I find Firefox much better than Safari in terms of features especially "Extension" like Web Developer Toolbar. RSS feed live bookmark is also one of the feature I find it very useful. I hope with the release of Tiger, Safari can catch up with Firefox in terms of cool new features that will enchance our browsing experience. I have tried both Safari and Firefox but I find Firefox much better than Safari in terms of features especially "Extension" like Web Developer Toolbar. RSS feed live bookmark is also one of the feature I find it very useful. I hope with the release of Tiger, Safari can catch up with Firefox in terms of cool new features that will enchance our browsing experience.

]]> By: Ralph Scheuer http://nslog.com/2004/11/10/qotd_firefox#comment-12456 Ralph Scheuer Thu, 11 Nov 2004 08:57:12 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12456 Another thing that bugs me about Safari: you cannot build backtracking-safe web apps and rely on its behavior because in general, Safari has a tendency to cash too aggressively (in fact, its entire behavior upon a "return null" in WebObjects is unreliable) and moreover, the Javascript and DHTML support in current incarnations still sucks at times... Another thing that bugs me about Safari: you cannot build backtracking-safe web apps and rely on its behavior because in general, Safari has a tendency to cash too aggressively (in fact, its entire behavior upon a "return null" in WebObjects is unreliable) and moreover, the Javascript and DHTML support in current incarnations still sucks at times...

]]> By: Ralph Scheuer http://nslog.com/2004/11/10/qotd_firefox#comment-12455 Ralph Scheuer Thu, 11 Nov 2004 08:51:38 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12455 Yes, I do. There are basically three reasons for me to use Firefox: MIDAS (htmlarea), the fantastic Web Developer extension and compatibility testing. I hate shitty XUL interfaces and I couldn't care less about it myself. However, at work I have the privilege of developing on the Mac, and therefore I need Firefox for the above reasons (one of them will be going away soon because Camino will get MIDAS). Another reason to care is that I sincerely hope it will take a lot of market share from IE on Windows - it's so incredibly annoying for our web designer to code around all those glitches in IE - maybe Firefox will help us to tell our customers one day "well, our applications are built for modern browsers, you know..." - I don't say it will happen, but hey, one can at least dream ;-) Yes, I do. There are basically three reasons for me to use Firefox: MIDAS (htmlarea), the fantastic Web Developer extension and compatibility testing. I hate shitty XUL interfaces and I couldn't care less about it myself. However, at work I have the privilege of developing on the Mac, and therefore I need Firefox for the above reasons (one of them will be going away soon because Camino will get MIDAS).

Another reason to care is that I sincerely hope it will take a lot of market share from IE on Windows - it's so incredibly annoying for our web designer to code around all those glitches in IE - maybe Firefox will help us to tell our customers one day "well, our applications are built for modern browsers, you know..." - I don't say it will happen, but hey, one can at least dream ;-)

]]> By: isle.yi.org http://nslog.com/2004/11/10/qotd_firefox#comment-12454 isle.yi.org Thu, 11 Nov 2004 04:57:28 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12454 I guess I would say "yes", because I like having choice. Whether or not I choose to exercise it, is another thing entirely. Personally I find Safari's interface disgusting and horribly unintuitive, and way too simple. When I first tried it, I expected clippy to jump out at me and tell me how to click on a link. Of course, you may feel different. The "it doesn't fit in on the mac" common complaint didn't even dawn on me as a possibility until I read it on a web page somewhere. It borderlines on nit-picking. I apologize for the callous remarks, but quibbling over UI when in reality, the renderer is what matters is pretty silly. And FireFox 1.0's javascript DOM implementation on the mac is really damn slow. I guess I would say "yes", because I like having choice. Whether or not I choose to exercise it, is another thing entirely.

Personally I find Safari's interface disgusting and horribly unintuitive, and way too simple. When I first tried it, I expected clippy to jump out at me and tell me how to click on a link. Of course, you may feel different. The "it doesn't fit in on the mac" common complaint didn't even dawn on me as a possibility until I read it on a web page somewhere. It borderlines on nit-picking.

I apologize for the callous remarks, but quibbling over UI when in reality, the renderer is what matters is pretty silly. And FireFox 1.0's javascript DOM implementation on the mac is really damn slow.

]]> By: Samual Icky http://nslog.com/2004/11/10/qotd_firefox#comment-12453 Samual Icky Thu, 11 Nov 2004 04:45:55 +0000 http://nslog.com/2004/11/10/qotd_firefox/#comment-12453 I'll chime in... Yes I care! Kinda. I can't stand Safari at all, so that limits my browser choices off the bat. I'm not going to go into those issues... but I've removed Safari.app from my System. I however don't think that the "roadmap" should have been changed for Firefox. Last week they, m.o looked at the versiontracker reviews and thought hay lets shipp the mac version as is... people really seem to like it over safari. Well that was the cover. All the Aquafaction that was planned would strach well into March of `05... and they really want to get everything back to the truck... so what happens roll Aquafacation back to Firefox 1.1 which would ship around the same time as the Mac 1.0 would have. As a result we get the heaping mess that m.o calls Firefox for Mac OS X. Oh and I use Firefox for OS X daily... my main browser of choice. Oh and Dave you make a horriable jump in logic... Camino isn't spliting resources. M.o has no control over the projects persay... Camino (Camino started out to prove Gecko could prove to be a WebKit like interface before WebKit was a twinkle in Apple's eye) started before firefox so they can't just pretend it never existed and many people love Camino... Not all developers who work on Camino would drop what they are doing and work on the Firefox port. Some might never have worked on an Open Source project and some just might find some other Open Source project work on. I'll chime in... Yes I care! Kinda. I can't stand Safari at all, so that limits my browser choices off the bat. I'm not going to go into those issues... but I've removed Safari.app from my System.

I however don't think that the "roadmap" should have been changed for Firefox. Last week they, m.o looked at the versiontracker reviews and thought hay lets shipp the mac version as is... people really seem to like it over safari. Well that was the cover. All the Aquafaction that was planned would strach well into March of `05... and they really want to get everything back to the truck... so what happens roll Aquafacation back to Firefox 1.1 which would ship around the same time as the Mac 1.0 would have. As a result we get the heaping mess that m.o calls Firefox for Mac OS X.

Oh and I use Firefox for OS X daily... my main browser of choice.

Oh and Dave you make a horriable jump in logic... Camino isn't spliting resources. M.o has no control over the projects persay... Camino (Camino started out to prove Gecko could prove to be a WebKit like interface before WebKit was a twinkle in Apple's eye) started before firefox so they can't just pretend it never existed and many people love Camino... Not all developers who work on Camino would drop what they are doing and work on the Firefox port. Some might never have worked on an Open Source project and some just might find some other Open Source project work on.

]]>