Mozilla M17 Is Out
As the title says - Mozilla M17 is out. Release notes are available at that Web page as well. As usual - please test it and submit bug reports.. (please note: this is NOT the nightly build that was posted here previously). Update: I just got note that Netscape 6.0 PR2 is also out. Netscape bug reports should be reported here only!
More to the point, there shouldn't be an install at all. I want a full download. This sucks. Maybe Americans just forget that Internet access costs us money in Europe. Phone calls aren't free. Normally, I'd download stuff like this using the leased line at work, burn it to a CD and take it home. With poxy installer programs like this, that's no longer an option :-(
"The invisible and the non-existent look very much alike." -- Delos B. McKown
When will someone make a Mozilla-based browser that works with XView? There are still some people using olvwm and this much-underrated toolkit..
The PR2 release is a complete disservice to the mozilla.org community. There are really two products here, the Mozilla browser and the Commercial browser. The Mozilla browser is a very fine product. The Commercial browser is a steaming pile of shit. Unfortunately, Mozilla.org, the makers of the Mozilla browser, are going to get skewered by Slashdot and trade press magazines because the Commercial browser, which is made by AOL, is such a joke.
Why is the commercial browser so lame? From out site of the walls at AOL/Netscape, I can only guess. But I can tell you that as an active tester of the Mozilla browser, Netscape Product Development Team's bug-fixing priorities are infuriating. Hours before the release of this PR2, I filed two "smoketest blocker" bugs. This is the most severe kind of bug, and should have prevented the release of the browser. A blocker is a bug which prevents the browser from passing the defined smoketests. These are tests of basic functionality. Not passing these tests means that the browser is not ready for release.
These two serious bugs were marked, by AOL/Netscape people, as "MOZ ONLY", which essentially means "to hell with you we're releasing the product anyway." Of course, the product is released, and the Linux installer doesn't work at all if you have bash2, and the browser will dump core if you try to load ftp.netscape.com in a particular way.
The quality control process at AOL/Netscape has completely failed. They do not follow the quality guidelines of the Mozilla project, as defined on the Mozilla web site. By releasing the Commercial product in such a sorry state, they have embarrased everyone who works so hard on Mozilla, and I suspect that they have lowered morale across the entire project.
Shame on you Netscape.
(I just posted this to Mozillazine. Note that most of this has to do with the Netscape repackaging of Mozilla, not with the Mozilla browser/platform itself)
.sit in less
Well I guess I'm the first one to review this for the Mac.
HOLY CRAP. We're in trouble.
All I can do is hope to holy hell that Netscape buries this release and no one in the general public ever downloads/installs PR2, ever.
Oh, and by the way, let me say in advance to whoever will argue the usual "this is pre-beta
software, blah blah blah blah" let me remind you that THIS IS THE FIRST EXPOSURE MANY
PEOPLE ARE GOING TO HAVE WITH NETSCAPE 6. Their opinions will be formed largely
on their earliest experiences. The fact that netscape has released this is.. oh jesus....sweet jesus help
us.
I'm sorry, I'm still just totally stunned.
Let's start off with the download/install. I loaded the installer (very small, admittedly, though it
was located in a directory labeled for Mac OS 8.5. I use Mac OS 9, but after downloading the
readme confirmed it worked on 8.5 OR ABOVE) and took a look inside the folder. There's a
README file with astonishingly dry, boring installation instructions, and there's a License
Agreement file. No personality whatsoever. Nothing discussing this as an open source project,
nothing about what this release is for, no notes about reporting bugs, and no reminder that what
you're about to see is a work in progress and you can expect that it's going to be fixed and check
out a nightly of mozilla and if you want to help build it, here's what you do and....on and on.
What a totally missed opportunity to introduce the project.
Anyway, so I ran the very unappealing installer which asked me which components I wanted to
load (I have no need for German, wanted to try a mail/news free install, etc.)
1. It then installed everything, totally ignoring the components I selected.
2. It took about 50x
longer to download than the Mozilla nightlys. Why can I get the whole of Mozilla's
than a minute on my DSL, unstuff and just run, but to get Netscape I had to go through a whole
rigamarole of downloading each peice, then processing them all which took over 10 minutes?!
(don't tell me the bigger size is the reason either. The "extras" might account for a little more
time, but not this astounding install-a-thon)
3. It then ran a profile manager thing and then, at my
foolish request, converted my Netscape 4.x profile to Netscape 6. This took, on my Powerbook
G3 about 5 drive-churning minutes.
4. Finally it finished. It then asked me to enter all kinds of
bizarro Netcenter-related stuff. I THINK I have a netcenter account (that's my.netscape.com,
right?) so I entered some info, which it took without asking for a password or anything. All I
have to ask is-- what the hell was it going on about? I just wanted to try the browser, not apply
for an East German exit visa.
5. FINALLY after more whirring churning, gurgling and spinning, I finally got something that looked like a browser, albeit wearing the CRAPPY "modern" skin.
6. Displayed on the screen was a totally ugly page with some kind of layered animation that was
moving so slowly I could see the redraws. The computer felt like it had ground to a halt.
I should mention that the above process took about 15 minutes. A typical Mozilla install for me
is, oh, maybe 3 minutes from download to running it. During the install, there was no caveat
about (1) how the zillions of files were temporary and that (2) I can expect vast improvements in
future versions and that (3) gosh, you can help with this fun internet experiment, and here's how.
In short, the installation experience just plain sucked.
I should also mention that PR2 starting up for the first time on my Mac feels about 1/3 the speed
of Mozilla's recent builds. The AIM client in the sidebar made me laugh out loud it was so slow
and awkward. After getting no response from double-clicking a buddy's name a few times to
send an AIM too, I suddenly locked up as about 9 IM windows slowly tiled themselves on the
screen. I stopped laughing and my jaw just hit the floor.
I must also add that during the install, the fake non-native widgets looked totally half-baked. I was
having flashbacks to Mac's infamous Word 6 port. I swear to god Java's Swing looks about 5x
classier than this awkward mess. Netscape, can you at least use "Classic" for the installer part so I
can see some normal looking buttons?
When i finally switched to the classic theme (the preferences wouldn't open at first, and then after
I selected it, I couldn't hit the OK button, I had to Cancel) things looked MUCH better, but it's
still abominably slow.
WHY OH WHY doesn't this default to classic?
Anyway, I honestly don't know what Netscape is thinking. I'm have a feeling this will be one of
the kinder reviews by a Mac user in the next few days. (I *LOVE* the Mozilla project you
guys...)
To anyone who may have come here who is not really familiar with Mozilla, please do NOT
judge Mozilla on the Netscape PR2 release. It doesn't have to be like this...
Wait for PR3, or go grab one of the M18 nightly builds: (LINK) -- it's a lot better.
W
PS - I hope that they've got better bug report handling than they did for PR1 cuz I have a feeling
they'll be overwhelmed.
PPS - Sorry for anyone I've offended. I'm still a believer in this project, and if I made any errors
I'm sure they'll be corrected quickly.
PPPS - Stupid new menu items of the day: "Print Plus" (?!!!!)
-------------------
-------------------
This is my SIG. There are many like it, but this one is mine.
- ftp ftpi.netscape.com
- cd
/pub/netscape6/long obvious path/
- grab all the files (recursivly) including the xli and lps directories
- set up a FTP server locally to mirror above directory structure
- edit hosts file on machines to install, point ftp.netscape.com to be host of your FTP server
- run their install, and it goes local
- take ftp.netscape.com out of hosts file
Of course, could do DNS tricks to do the same...If you READ the release notes, you'll notice that it says:
"The M17 development cycle included the last of the major feature work
that is planned for Mozilla 1.0 From this point forward the development
focus will be performance, stability and footprint."
So, the point is that performance, stability, and footprint are going to be the focus for the next milestones. Anything confusing about that?
I really like IE5. It's easy to develop for,
Huh? Why would you develop for a specific browser? Just follow the standards, and your stuff should work with all browsers.
Well, obviously, most browsers have some standards deficiencies, but usually they're in areas that you don't really need to be using anyway.
I think the real problem is that web page creators think they're "developers" instead of "authors." The web is about information, not programming. If you're putting more effort into JavaScript than into your content, your site will suck. If someone goes to your web site with Lynx, will they still find it just as useful, even if it is less cool looking?
--
Sheesh, evil *and* a jerk. -- Jade
I'm a big IE5 fan. I think it is stable, fast, and reasonably standards compliant - despite the general view on Slashdot. I doubt anyone can argue that it is better than Netscape 4, anyway.
I tried Galeon the other day. If you haven't heard of this, it is a GNOME/Gtk based browser, which uses the Mozilla "Gecko" rendering engine. I was very impressed. You remember all that stuff everyone was saying about how Mozilla was going to be the fastest render on the block? Well.. it's a close call, but I'd say Galeon is pretty close to achievig that now (This with is M16 - it might be quicker now).
As for startup time (always the problem with normal Mozillas) - it is now much, much quicker than Netscape 4 on either Windows of Linux, and getting close to IE5 (which is the fastest starting browser I've ever seen, except maybe Lynx or something).
It's not quite ready for everyone to use - there are a few niggling problems (no animated "Page Loading" icon so you know when it is doing something for instance).
The cool thing is that using this doesn't stop you from using XUL as well. For instance, I used it to ftp a file, and was surprised to see a new window pop up with a XUL based download monitor.
Very Impressive. If you can't wait for the Mozilla UI to get better, give this a go. At least it will start putting a few "Mozilla 6" in web server logs around the place.
Oh yeah.. I found you needed Helix-Gnome for it to work correctly on Redhat 6.2
All praise the mighty lizard... for the first time, Mozilla has displayed the PNGs at http://www.libpng.org/pub/png/pngs-img.html flawlessly. Good work, Mozillans!
Mozilla maintainers - please, PLEASE, when you are creating a mozilla tarball, make the top level directory something like "mozilla-M17", or even "mozilla". When I untar that archive, I do NOT expect it to create a directory called "package". Please follow the lead of every other well-behaved program installed from tarballs.
</rant>
I'm a leaf on the wind. Watch how I soar.
If you don't want to use the installer to download everything, just do it yourself - grab everything in the xpi directory and copy the installer to your local xpi directory and run it. No more autodownloading...
Mozilla is has been rewritten and shares no code with Netscape. Netscape 6.x releases *are* Mozilla releases.
I skipped the initial suck.com discussion, but I'll bite here. Let's face this fact: Microsoft can't be beaten on its own platform. Mozilla, however, is intended to do all the things right that both IE and Netscape did wrong. That costs time and you know it! There's a reason that features are being added.. /dev/null until the Mozilla crew actually made it to 1.0! I tested yesterday's nightly build and except for keyboard shortcuts not being working under Linux, I thought Mozilla was fast, neat and stable. Give it a try and help Mozilla rather than just asking to bury it. Shame on you.
It seems to be fashion to claim that Open Source is slow and never releases something final, and that's just plain FUD. Because you, and I, and Suck are users and not developers, we have the right to beg and complain about final releases. But please, keep this Suck marketing shit in
Just like the subject line says. Of course Netscape 6 sucks ass, it's made by AOL, the same fine folks who brought us that helpdesk nightmare and lawsuit waiting to happen, AOL 5.0. Seriously, no one can blame Mozilla for AOL's incompetence. And, I don't care if Netscape 6PRwhatever is going to be most people's introduction to Mozilla, because there's still plenty of time for Mozilla/Netscape 6 Final to prove themselves. After all, did you ever run Netscape 0.9, the prerelease version of Netscape 1.0? It was horrid, horrid, and evil, and made Mosaic look like the future of the Net. Or, ever run early versions of IE? My GOD, the hooror that was IE before way into version 3.x still haunts me in my dreams.
Fact is, these days people are more adventurous about what software they install, as evidenced by stuff like Neoplanet, the front end for IE which many, many people download just to get skinning functionality, and other eye candy like WindowBlinds (think Enlightenment for Windows). When Mozilla gets final, people will download it, and people will be pleased. They'll not only get skinning, but more/better functionality than IE, and other useful integrated apps. All in all, this snafu has absolutely no effect on the viability of final releases of Mozilla/Netscape and their future popularity, except of course for the fact that AOL will probably fuck it up again when they release Netscape 6.0 final.
And as an aside, why the flying fucking sweet mother of jeezus h. christ would anyone want to install over the net, DSL or no DSL, when the sane thing to do is just download a complete installer and then work from there? that's a very disturbing trend I've been bothered by. For the love of God, you should always download a whole installation program, and store it for possible future use. Why would anyone want to risk getting disconnected during install, or getting a slow connection to the server during install, or having to download the whole thing over again later for a re-install? I think people are getting too used to getting programs for free, that they no longer bother to keep potentially useful installers around. After all, the version you love of a piece of software might be a pain in the ass to find a good ways down the line, but if you keep a local copy you'll never have to download again barring tragic accidents. It especially annoys me when companies make only the barebones installer easy to find, hiding the complete package on the server someplace; Apple has done this with Quicktime, making it difficult to find the full installer, but linking the Net installer all over the place. People ought to complain loudly about such foolishness.
And some of the problems you mentioned were possibly due to poor multitasking by MacOS; as improved as OS 9 is, it still has very poor multitasking. All it takes is too many processes running, and it'll sometimes choke and run too slowly. And, let's see--you were installing over the net, and that's at least two and probably more programs running; two or three programs can usually run fine, but any other running apps could have contributed to a slow system. And then, after it had installed and you were running Netscape 6PR2, how much stuff altogether was running, in addition to Netscape and AIM? AOL deserves most of the blame for their ineptitude, but never underestimate the ability of MacOS to bog down because of poor multitasking, either. OSX will fix that for good, but it's a little late--shitty multitasking in MacOS was one of the big reasons I switched to Windoze.
"The more corrupt the state, the more numerous the laws."--Tacitus, *The Annals*
Java being missing is not Mozilla's fault: see this bug report
Ack - okay, so this is actually being posted from PR2. That's not bad. PR1 wouldn't even run long enough to get here, but we'll see.
Just some opionions right off the bat, though:
First of all . . . fix the installation, folks. I selected a really minimal custom config. and what did I get? EVERYTHING. This is just bad. I din't want any stinking AOL crap, or instant messaging, or whatever. And I already have Java, and I develop in it, so don't install another JRE for me, please. Whoops, too bad.
That initial annoyance asside, let's look at some nice things. Namely, the interface. I actually design interfaces all day long, and this one isn't all that bad. The widgets are a step above the standard win32 API, I must say. Had to tweak it do death though because it had so much clutter! Ick.
But worst of all, what the hell . . . isn't this a browser? Can't we just have a browser by itself? I already read my mail with something else, I already use Instant Messaging with something else, and I really don't need another program taking up space to do these things! And if I wanted to register with your crappy Netcenter home pages, wouldn't I? Do I have to click past 3 screens just to tell you NO!?
But rants aside, it's getting there . . . still slow, still renders a whole lot incorrectly, but hey it IS a preview.
--
Cherish. Live. Dream.
And up until this release, I thought that seamonkey sucked. However, this is a very stable release. It's much easier than IE to install. It was a mere 6 meg download, and installed in about 2 minutes. The load time is also about 3 times as quick as the last release (which, if I remember correctly, took 17 seconds to load on my computer). It's also far less buggy. I've managed to post this, haven't I?
Another thing that impressed me was the time it takes to parse a web page. M17 kicks IE's tail (and, quite obviously, NN4.x). The slashdot home page takes 6 seconds to parse on IE, and only 1.5 on M17.
Before this becomes widely used, however, I think that the following things need to change:
I applaud the Mozilla team. They've taken what I thought was an unreal fantasy, and turned it into a reality. Minus some minor bugs, this browser is already on par with IE. Now the real battle will be to get it into widespread usage.
--
I'm sorry. The number you have reached is imaginary. Please rotate your phone 90 degrees and try again.