What Netscape Needs to Succeed
Monday October 26th, 1998
This week's editorial touches on four possible strategies Netscape could use to recover lost ground. I believe it is possible, but it won't happen without some serious introspection. Click Full Article to read more.
Update: Some of my opinion has come to fruition today, as you will see when you read the article...
#10 What Netscape Really Needs to Succeed
by tumbleweed <firstname.lastname@example.org>
Tuesday October 27th, 1998 4:29 PM
You are replying to this message
What Netscape *really* needs to succeed WITH NAVIGATOR (I'm not talking about the company as a whole, just with the whole Communicator/Navigator situation), is to first: figure out what the customers really want. I don't think that's ever been done at Netscape.
When people complain about browsers, they almost always complain about stability, speed, and what enormous resources they need to install and run.
The average user couldn't explain why IE is vastly superior ON PAPER to anyone, yet they can easily compare browsers by which one runs faster, crashes less, or which one simply refuses to install on their old Macintosh.
The new Navigator will solve all (?) the technical inadequacies by adding HTML 4, DOM, XML, and improving CSS. And the massive open source effort should definitely alleviate the stability & speed problems.
As far as the resource requirements go - that's a matter probably best solved by making different versions of the browser available (still no standalone of v4.5, huh? *frown*). I can't help but wonder where we'd be now if the concentration on the unified front-end and the NGLayout engine had been the priority from the start of the whole effort, but oh well, better late than never. And better a late release than yet another browser incorporating new features people don't want that & that doesn't fix bugs that have been present since pre-1.0 (like what happened with v4.5).
Never let it be said I didn't have an opinion! :)