Which validates my statement. Do not download 6.2.1 until the next release.
Bamm Gabriana typed: >>No killfilter on usenet? That is a big issue. > > It is a big issue. It will be added soon. But don't expect it done > in 1.0. The purpose of 1.0 is to provide an API freeze, not a > final end-user product. > > >>High memory usage? That is a big issue. > > It is being worked on. Btw, Netscape 6.2.1 uses over 3 times > as much memory than Mozilla nightly 2002030803 which I am > currently using. > > >>Abandonment of theme development on 6.2.1? Shitting on users > > The theme format has changed. But 1.0 will provide an API freeze, > meaning formats will not change from there on. When Netscape 6.5 > comes out (which will be based on Moz 1.0) you can build themes > which will be guaranteed to work with all future versions of NS. > > >>Giving you a worthless version of Real Player? That is a big issue > > I am using Moz nightly 2002030803 and I don't recall having Real > Player installed. Perhaps we are using a different browser. Netscape 6.2.1, not Mozilla. > > >>Having to register it? That is a big issue > > I am using Moz nightly 2002030803 and I don't recall having to > register it. Perhaps you are complaining about the wrong browser. > > >>Mega problems with Communicator moving their settings to it? >>That is a big issue > > I am using Moz nightly 2002030803 and I don't recall having > problems moving my Communicator settings. Perhaps you are > not using Moz. I mentioned Netscape 6.2.1 not Mozilla. > > >>AOL refuses to use it on 7.0 when they could of? That is a big issue. > > Because it still doesn't have a frozen set of API's. AOL is waiting > for 1.0 so they could use it. > > I disagree totally. AOL is not waiting for 1.0 to use with it's products.
