Since Leopard came out, I don't think I've even loaded FireFox or Camino. I haven't seen anything that doesn't work in Safari 3 and it's super fast compared to FireFox. I doubt I'll go back at this point, I see no reason. I will probably even remove them from my system.
I've even switched to using Safari on Windows for general surfing -- that's a twist I never expected.
Matthew J
· 1 year ago
Agreeed, that is bad news. But the fact still remians that from a development (tools) standpoint there is still nothing better than Firefox, so I as a developer will be stuck.
You can always choose to run an older patched version such as 2.0.0.7 or something along those lines!
Jon Clausen
· 1 year ago
I still use Firefox as my primary browser for the developer tools and plugins, but I think it's becoming a victim of it's own success. Features seem to be the main focus, at the expense of stability.
Frankly, I never understood why Camino was a necessary development product. Seems like they could have deployed those resources on making a better, faster, more stable Firefox for the Mac.
Connie Bensen
· 1 year ago
Have you tried Flock? It's Mozilla's newest...
I see that we're both speaking in Seattle at the Web Community Forum. I look forward to meeting you!
Paul Kim
· 1 year ago
Hey Jake - The mashable story was based on a misleading article that made it sound like we're ignoring 80% of *all* the bugs we've fixed in Firefox 3. The reality is we've already made over 11,000 bug fixes (including feature and performance enhancements) in the code for Firefox 3. I'd encourage you to read the details here.
Jeremy G
· 1 year ago
The story of "only 20%" of bugs getting fixed before released was not true. Mozilla has already announced the fix of 11,000 bugs, with 700 issues still being discussed. I don't recall the source of the 20% claim, but it wasn't from Mozilla. I know that at least CNN has begun to acknowledge the inaccuracy of that story.
Mike Shaver
· 1 year ago
Camino is developed by the Camino development team and community; it's not a product to which the Mozilla Foundation devotes resources, other than fixing bugs that they find in the core code, and providing server resources for things like source control and builds. I don't think that ignoring those (few) bugs or denying the Camino community those server resources would have any positive effect on Firefox, but I suppose someone might think otherwise.
As an aside, you shouldn't forget that you can participate in Mozilla's development directly, from layout engine to front end to testing to localization to user support; you're not restricted to hoping that things will go as you would like, or complaining if they don't, and we have literally thousands of people with no other software development experience who help us every day to improve Firefox and our other work.
I'm a little saddened that people would read a single article somewhere describing a very significant change in development philosophy and just take it at face value, when it's really so easy to find someone directly involved in the project or go to primary sources. (Not picking on you, Jake, as it happens a lot. I think a lot of people just aren't used to the fact that the developers of a major piece of their software arsenal are actually transparent and available.) Hopefully this round of (honest) error and correction will encourage people, bloggers and journalists alike, to dig a little deeper before sounding our death knell. :)
All Comments
I've even switched to using Safari on Windows for general surfing -- that's a twist I never expected.
You can always choose to run an older patched version such as 2.0.0.7 or something along those lines!
Frankly, I never understood why Camino was a necessary development product. Seems like they could have deployed those resources on making a better, faster, more stable Firefox for the Mac.
I see that we're both speaking in Seattle at the Web Community Forum. I look forward to meeting you!
As an aside, you shouldn't forget that you can participate in Mozilla's development directly, from layout engine to front end to testing to localization to user support; you're not restricted to hoping that things will go as you would like, or complaining if they don't, and we have literally thousands of people with no other software development experience who help us every day to improve Firefox and our other work.
I'm a little saddened that people would read a single article somewhere describing a very significant change in development philosophy and just take it at face value, when it's really so easy to find someone directly involved in the project or go to primary sources. (Not picking on you, Jake, as it happens a lot. I think a lot of people just aren't used to the fact that the developers of a major piece of their software arsenal are actually transparent and available.) Hopefully this round of (honest) error and correction will encourage people, bloggers and journalists alike, to dig a little deeper before sounding our death knell. :)