Mozilla Poised for Revival? 430
MarkedMan writes "An interesting and fairly lengthy CNET article on Mozilla and the pending 1.0 release. Kind of shallow research, making some common mistakes (Like many others, he half implies that AOL picking Mozilla as the default browser automatically puts 35 million users in the Netscape camp.) Good to see this getting some fairly mainline press."
All right (Score:3, Interesting)
Even if (Score:2, Interesting)
Would be nice if you could count on 35 million to just switch at the drop of a hat... but howmany are still using AOL3, 4,5,6 etc...
Just proves Joel's point (Score:2, Interesting)
I know that as a software developer, I've certainly learned from Netscape's mistake.
Re:Netscape is dead (Score:5, Interesting)
While this was actually true to some degree in the early days of the Mozilla project and the later days of the IE project (IE 6 is almost respectable...for a Microsoft project), I believe Mozilla has surpassed Internet explorer in several areas that are important to at least myself. For one, as a sometimes web developer, Mozilla sticks closer to the standards. I've found myself on more than one occasion having to go back and figure out how to crap-up my HTML code to make it look right in IE. That's a waste of time, but because of people like you, and companies like Microsoft, I have to do it. Further, when I used to use IE back in the dark age of my OS use (i.e. Windows...also note that that i.e. has no relation to IE. In fact, even i.e. is embarrased by IE), I used to open up new windows like crazy! With tabbed browsing in Mozilla, I can keep a single instance of Mozilla open and keep all the sites I'm at organized! I'm never using a browser without tabs again!
For these and other reasons, I truly like Mozilla better than IE...even better than Navigator as well, as it seems less bloted than Communicator 6.0.
It'll be a victory for standards. (Score:5, Interesting)
Some interesting weblogs by mozilla developers (Score:5, Interesting)
Mozilla is flexible and everywhere (Score:3, Interesting)
Mozilla an alternative, not a competitor. (Score:2, Interesting)
I run linux 99% of my uptime. And I use galeon on top of Mozilla. Why? Not because I hate the concept of IE (I hate IE for other reasons) but because it's an alternative. Sure I have a Sun that I could run IE on, but the velocity of the Mozilla and Galeon development is the alternative solution that I'm looking for.
OpenSource developers aren't "let's go give MS a run for their money!" people. They're "let's go make a browser that sucks less." Not everything is a competition - some projects exist just to provide alternatives.
What is Python a competitor to? I dunno... It's just an alternative... Just like Mozilla...
-c
FWIW (Score:3, Interesting)
If AOL uses Moz, that'll help it gain acceptance much more quickly. Ask yourself where IE would be if Netscape had played nice with AOL all those years ago. Okay, probably still on every PC, but it'd be sharing much more mindshare with Netscape.
Missing the server (Score:2, Interesting)
Yeah yeah yeah - quote netcraft at me with Apache = 60% and so on. I believe it too, but it doesn't matter. *MANY* commerce site - the things your parents and friends visit - run on IIS (for better or for worse). You can argue percentages all you want, but there's enough of them out there. Heck Macs are about 5% of the computer market, but some people still care about them.
If you even concede that IIS has a 15% share of servers conducting commerce, that's a big number.
My point? If mozilla ever starts to be a credible browser threat, IIS7 (or 8 or whatever) will suddenly either not work with mozilla at all, OR give lower priority treatment to mozilla requests. Or, better yet, just occasionally drop requests, making it even harder to diagnose.
"Works fine when I use IE7.5, but danged if Mozilla 1.01.02RC3 (cause that's about where they'll be) crashes sometimes!"
There's already issues with SSL between IE and Apache servers and non IE browsers and IIS. MS controls too much on both sides - IN BUSINESS/COMMERCE, WHERE IT COUNTS - to ever let anything else ever get too big again.
Responses?
Kmeleon comes along? (Score:1, Interesting)
The "risk" associated with mozilla becoming mainstream is that we would be more subject to spyware attacks and such because the user base has grown so that it is significant. And frankly, as much as we talk about mainstream acceptance, many of us will not like the other side effects of mainstream acceptance that I have mentioned.
If Mozilla does become mainstream, I think that there is a possibility for a K-Meleon [sourceforge.net] revival and a port of the browser to linux. K-Meleon is a gecko based browser with many features similar to mozilla but it is "light" and does not have the news/mail/composer stuff in it.
So am I right about many slashdot users in the idea that they prefer to stay in the obscure corner? Reply to this!
Re:Just proves Joel's point (Score:3, Interesting)
Re:All right (Score:3, Interesting)
Wishful thinking. These AOL users will still have Internet Explorer on their machines. A good majority of them will just change their AOL options to use IE instead of Netscape once they upgrade to a version that defaults to Netscape. They may not be completely computer literate, but they aren't morons...
I think you are overestimating AOL users. The majority of AOL users use AOL because they don't know how to work a computer. That's AOL's big selling point, that they don't have to think.
At any rate, neither DHTML nor CSS are IE specific features, so you have no idea what you're talking about to begin with..How did your post get moderated up?
How did your post get modded up? IE uses proprietary tags not found in the WC3 standards to implement "features" exclusive to IE. Many web sites use these tags that only work in IE.
This has been going on since the earliest days of web browsers, and in the past both IE and Netscape were just as guilty of inventing proprietary tags to give their browser more "features". That is what is so great about Mozilla, it is the most standards compliant web browser available. Now developers can code to the WC3 standards and know there is a browser capable of displaying the page correctly. Once (if) AOL converts their users to Mozilla it will hopefully force MS to make IE more standards compliant and in return allow developers to finally be able to easily design browser agnostic web sites.
Obviously you don't have much experience dealing with either end users or web page design issues.
Dumb question - is Mozilla worth it? (Score:2, Interesting)
Slow as molasses. Tuned it a bit, but it's still dog slow.
I hate IE - but I need something that uses my DSL and doesn't take 60 seconds to render an email or bring up a page.
Is there much difference between the Mozilla 1.0 build and the Netscape 6.11? Should I have chosen native Win code during the install instead of "generic" code?
Are there any useful sites to help with this - and what are their URLs? And does anyone know how much of a difference (stats, URLs, basic ratio) there is between the Netscape build and the Mozilla build?
Yes, I tried Google - and it helped a bit in tuning some things. But I've got a Qwest DSL line, and it's dog slow now.
-
funny browser compatibility experience (Score:1, Interesting)
I emailed their customer service and they said "Netscape does tend to be a little quirky. We suggest using Internet Explorer or the most updated version of Netscape."
It just so happens that I had IE5 and Netscape 6 on my machine so I tried doing the transfer with both app's and got the same error. I emailed customer service again, and here is the response (word for word):
"Have you tried Internet Explorer 6, as that is the most recent and should solve your problem. That is actually what 95% of our Customer's use who access our website. Thank you."
Can you imagine that? Think they were blowing me off?
I can only imagine the kinds of reponses from customer service folks who have never heard of Mozilla:) btw-Downloaded Mozilla for my home computer the other day, running on OSX and have been very pleased so far!
Mozilla is awful... and not (Chimera) (Score:1, Interesting)
Is it just me... (Score:2, Interesting)
1. It is not really a "real" 1.0 release
2. It has always been buggy and not useable
3. It is not as mature as IE
4. AOL might switch to it, but only because of sour grapes
5. Its history shows it is unreliable
6. No one in their right mind would trust their future in Mozilla.
Maybe I read too much into it, but that was the sense I got. As someone who has been using Mozilla on Windows, Macintosh, and Linux since 0.8 or so, none of this has been my experience. It is more solid than IE, faster, and very reliable. It now has at least as many features as IE and crashes almost never on any of the platforms I have used it on.
W3C Validator (Score:3, Interesting)
I don't know, that thing is awefully picky. It doesn't even validate with the Mozilla [w3.org] web site (although it is possible [w3.org]). Are the Mozilla developers bad at web development? Perhaps. More acurately, I think a good web site doesn't necessarily have to follow all the W3C standards (although it is nice, I suppose).
I've seen countless web sites that display very well in Mozilla that get torn apart by the validator. I know, by ensuring W3C compiance you can be sure it will work in almost all browsers, but I don't necessarily care. I only worry about Mozilla and Internet Explorer. (Sorry Opera users, but it's bad enough dealing with two browsers on 3 different operating systems.)
I guess that's not why I'm not a web development professional...
Re:W3C Validator (Score:3, Interesting)
The whole ideal behind standards is so that you (theoretically) shouldn't have to care about all the browsers.
From my point of view, if I design a web page and follow the standards to the "t" and verify it for compliance after every single minor change, then if a browser doesn't render my page properly the browser is at fault and I don't give a shit. It's not my problem.
Now from a more practical standpoint. If my web page is going to be making me money and 90%+ of my users are IE users then I better make sure it renders properly in IE. However, that's still no reason not to follow standards. Because if I make a concerted effort to follow the standards then I can be reasonably sure that any other browsers (that I haven't tested it with) stand a good chance of rendering it properly.
With the above stated there's absolutely no reason not to verify your pages for standards compliance with the exception of pure lazyness.
--
Garett