It's true, I tell you.

The fun thing with firefox is that if you know where to look you can find parts that neatly click onto your katana building a Swiss Army knife with just the parts you like best.

I personally prefer free (and Free) weaponry.

I love my Opera. Wouldn't bring it to a swordfight, but how often do those happen?:)

"When I was little, my father was famous. He was the greatest samurai in the empire. And he was the shogun's decapitator. He cut off the heads of 131 lords. It was a bad time for the empire. The shogun just stayed inside his castle and he never came out. People said his brain was infected by devils. My father would come home. He would forget about the killings. He wasn't scared of the shogun, but the shogun was scared of him. Maybe that was the problem. Then, one night, the shogun sent his ninja spies to our house. They were supposed to kill my father. But they didn't. That was the night everything changed."

Bram! :

> The fun thing with firefox is that if you
> know where to look you can find parts that
> neatly click onto your katana building a
> Swiss Army knife with just the parts you
> like best.
Yup. The annoying thing with Fx is that once you're done "clicking" things "into your katana", you end up with something that looks like a porcupine that has a katana in there somewhere and gobs of things welded to it, taped to it with a duct tape, stuck to it with a used piece of chewing gum, and tied to it by means of used condoms. And it acts accordingly. The worst part, of course, is that this mutant animal rolls over and dies every damn time that one of the other tools feels like getting rusty, stuck or broken, and then you have to start all over again...

What I'm trying to say, is that sometimes a quality swiss army knife is way better choice, especially if the katana itself is not very stable and its extensions API was designed so that the whole thing crashes without a warning if one of the extensions gets naughty... And they DO get naughty, quite often, in fact, because to date NO ONE BLOODY BOTHERED TO WRITE ANY EXTENSIONS DEVELOPMENT DOCUMENTATION!

Well, that, and the fact that the katana tends to grow into a 10 yards long rusty piece Godzilla would feel confortable with, by eating up all available system memory thanks to the "image cache" bu... er... "feature" and other equally "useful" bu... er... "features.

Grunt, I haven't experienced any of those problems, and I run loads of extensions on 3 PC's, 2 macs, and a Linux box. Strange.

To me, Firefox is the Multi-Tool (like a Leatherman Tool) of choice: It is handy, compact, can be taken anywhere, operates with precision, is loaded with tools, and can help you cut your leg off if a tree falls on it.

If katana is good, you can use it as beer bottle opener - just cut off these bottlenecks!

will :

> Strange.

Well, sorry, mate, but here's how it works : a piece of software (including the libs it relies on) is considered to contain bugs (same goes for crashers, naturally) if the software malfunctions (or CRASHES with no warning at all, respectively) for ANY user of that software, not just for will. So it's not that strange at all, will just got lucky - so far.

Grunt:

Understood. But what if it's the software that the software in question is running upon that causes the bug? And how can you be sure it's not?

will :

> But what if it's the software that the
> software in question is running upon that
> causes the bug?
"the software that the software in question is running upon" sounds like "OS" to me. Blaming NULL pointer access _inside Fx process_ on mystical "something" within OS-related processes that "causes the bug" (sic!) sounds kind of weak to me. You know, "the dog ate my homework" kind of "weak", or even weaker.

And if that "running upon" was your way of saying lib calls... Well, I'll be MIGHTY surprised if Fx 0.9.x (a piece of rushed BETA) will inadvertently expose a NEW Win32 API or e.g. CRT bug (the several rigs in question - at least those I tend to - are patched a-ok)... Not saying it's impossible, not at all. Just saying that those libs have been fairly stable for a while < wink-wink > ...

Grunt: OK you win with techno babble ;)

will :

"Win"? For me it was just a matter of "I call things as I see them...", not some kind of pissing contest, don't know about you... :)

"Techno babble"? My apologies then, I was assuming that since we were discussing what code might be buggy in this case ("Fx vs The World" :p ), both parties were coders. Sorry. (Even though, I suspect this stuff shouldn't be TOO foreign for you as someone who admin'ed *nix boxes. Which reminds me : strictly speaking, XML is NOT a "Programming Language", though I have a problem with deciding where it should belong on my resume as well :p. Speaking even more strictly, neither are the other three, especially the last one, but that's a bit of bickering : "programming language", "scripting language", "databases access/manipulation language", "database engine" - who cares these days! ;) ).

Yeah, I guess my resume needs some reorganizing. I lumped things together in the effort to keep it all short and simple. Thanks for looking and making suggestions.