Problems With the Firefox Development Process
An anonymous reader writes "Mike
Connor, one of the core Firefox
developers, is raising a flag concerning the Mozilla Firefox
methodology of development. From his blog: "In nearly three years, we haven't built up a community of hackers around Firefox, for a myriad of reasons, and now I think were in
trouble. Of the six people who can actually review in Firefox, four are AWOL, and one doesn't do a lot of reviews." In an earlier
entry, he raised concrete concerns about the community involvement. Asa Dotzler
recently elaborated
on the process, as previously covered on Slashdot."
Here is a funny diagram of the Firefox Development Process.
You're on a wrong web site, this one is for people with brains. Shut the fuck up.
what is it you're driving at?
FireFox is doomed! IE will rule!
Let me guess, he's going to expect everybody to call it "GNU/Firefox" from now on.
Clever programmer, but clearly nuts.
The problem here is that you're mistaking deep ignorance for knowledge; that is, you don't even know what you don't know. Firefox/Mozilla (and IE for that matter) do tons of things that Opera can't, and I make a pretty sweet living taking advantage of those capabilities.
That you don't understand what the capabilities of those browsers are doesn't mean that they're not there, any more than your inability to make use of them makes them useless to everyone else. It only means that your worldview is so narrow that you can't even conceive of most of what is happening out there.
Thanks very much for not mentioning some of those Firefox only features. For a minute there I was afraid your post may be insightful.
Maybe Mozilla.org should have avoided attaching their viral trademarks to every nook and cranny of the *open source software* with no ability to easily remove it. Are they still shipping third party copyrighted graphics too?