Slashdot Mirror
Mozilla 1.0 Officially Here
hhg writes "People of the world, rejoice! At last, the long awaited Mozilla 1.0 is released, and has emerged on the ftp.mozilla.org ftp-server. Let the release parties loose!" And there's even an Ann Arbor party now ;) Congratulations
to all the developers that contributed to the mighty lizard. And bahtama writes "The latest IE gopher hole patch is out! :) ... Check the release notes and then grab it from here."
http://www.mozillazine.org/articles/article2278.ht ml pretty much says it all :)
Congrats to all the hackers on the moz project. Fantastic job and well worth the wait.
In Soviet Russia...michael would be rotting in Siberia!
...of course, I'll use that new transfer protocol - TCP/IP over Flying Pigs.
...but I'll have to bundle up - my office just froze over.
..and maybe I won't have time - I think an attractive girl just mentioned that she may want to talk to me.
...but it's being eaten...by some...Linux or something...
First amazon.com had a profitable quarter.
Next, Slashdot sold out (Again)
Then, mozilla was released.
Coming up Warcraft III and Duke Nukem forever released.
Cm'on if you have 1.0_rc3 and you are not having problems, please do everyone a favor and DON'T download today...
Unless you are having problems.. try this weekend after the mirrors have had time to catch up!
While the ultimate goal of the Mozilla project is to produce source code that can be used by other projects and companies, the Open-Source project Beonex tries to make a browser for end-users out of it. (See Beonex vs. Mozilla). Beonex Communicator stays relatively true to Mozilla. Special emphasis is being put on security and privacy. The software is configured defensively, to avoid security holes to appear in the first place. For example, it sanitizes incoming HTML-email to the largest part.
The current version is available for Windows und Linux and bases on the final Mozilla 1.0 source code.
BTW: Congratulations to the whole Mozilla project!
Disclaimer: I am a member of the Beonex project.
I hope, Slashdot will also run this as main news article.
Please, don't use the developer groups for your questions. A good place for user discussion where you can ask for support or discuss and propose features is the new newsgroup:
snews://secnews.netscape.com:563/netscape.mozilla(Note that slashdot adds a space inside the link)
This source code is subject to the U.S. Export Administration Regulations and other U.S. law, and may not be exported or re-exported to certain countries (currently Afghanistan (Taliban controlled areas)
Bombing them is one thing, but not giving them access to Mozilla? That's just mean.
As long as Mozilla has its foot in the door with a significant niche of web users, as long as it is Free software that can never disappear simply because a company goes under, as long as it guarantees a viable browsing solution for all the platforms Microsoft would rather you forgot, then it has won. It will prevent Microsoft from completely dictating web standards, from creating a world where only Windows can browse the web.
The problem Microsoft (and others of its ilk) has with Free software is that it doesn't go away. When Mozilla first came out, there was a huge hype, but that hype evaporated and turned (in some quarters) to derision when Mozilla didn't deliver right away. For most MS competitors, that would have been the end. But Mozilla kept plugging along, getting better and better...it never has to go back to square one with a new company and codebase.
...and the longer it holds on with the high quality it has demonstrated so far, the more companies will jump on to its bandwagon. Everyone except for Microsoft benefits from open standards, and almost everyone knows it.
If a thing is not diminished by being shared, it is not rightly owned if it is only owned & not shared. S. Augustine
This bug is why mozilla insists on adding .exe extensions to anything delivered as application/octet-stream, .txt to text/plain, and likes to fool around with lots of other extensions depending on your exact setup (on my machine it tries to rename every mp3 file to .mpga).
314-15-9265
I want to personally thank everyone that downloaded Milestone and nightly testing builds and contributed feedback in the form of Bugzilla bug reports, TalkBack crash reports, comments in the newsgroups and at mozillaZine.org. And a special thanks to those people that gave a hours, weeks, months or years of their lives to the care and feeding of our bug database (triage and testcasing bug reports). Without Mozilla's amazing QA and testing community we wouldn't be where we are today. ;-)
Oh, and all the developers too
I'm using 1.0 right now, and the only thing that is annoying me is that 1.0 still uses that same (IMHO tacky) splash screen!
I fortunately replaced the splash screen on my copy at work (in Windows, drop a file called mozilla.bmp into the Mozilla directory, and that becomes your splash!) before I showed Mozilla off to my boss. Had he seen the regular splash screen, I don't know if he would have taken it seriously.
Seriously, the browser is professional, the splash screen should be too.
Please do not use the above mirror. It's primarily for use by the developers. If it becomes unusable they won't be able to get any work done.
I notice they're using the May 31st 1.0-branch build as 1.0 . I'm on the 2nd of June 1.0-branch build right now. Maybe they decided to junk several days' work due to mistakes.
:-)
Actually, we're already moving forward to Mozilla 1.0.1
--Asa
Near the end of the release notes, there is the warning
The bug report itself contains this pathetic comment:
that is to say... If Netscape can't use a Mozilla profile(and vice-versa) without causing nasty corruption then it shouldn't be trying. We should offer to import and create a new one without harming the old one - just like we do with other browsers that we like/share users with/ and support but with which we have incompatible profiles. (uhh 4.x)
Believe me, I'm overjoyed to mark bugs that stem from this behavior as invalid (and I will) but that doesn't strike at the core issue. Lots of users, QA, and developers have spent a ton of time chasing down these demons - no one knew of this incompatibility. Isn't there something to be done?
And yet in that post Linux is not mentioned once. Not even indirectly. Do you even know what Mozilla is?
Under the directory on the ftp server with the stub, there's an XPI directory which has the packages for the individual components. The install also has an option to save the downloaded files.
I don't mean to deprecate your efforts, but I think this "Mozilla isn't about producing an end-user product" idea has always been wishful thinking--and is becoming less plausible every day. Mozilla is clearly destined to become the prominent browser in the free software community and the web development community, and a popular browser among computer users at large.
I'm not saying it's a bad idea in principle to separate the development of the engine and the finish; I just don't see how it can happen in this case. The core features and the user interface of a browser are not separable enough. In order for Mozilla to produce a browser for testing purposes going to want it to be a good user interface. The evidence bears this out: users file usability bugs in bugzilla, the developers take them seriously, and as a result, vanilla mozilla has an overall better user interface than any earlier Netscape browser.
The Mozilla developers seem to agree on the value of a reference user interface, in order to prevent excessive variation in the interfaces of derived products. For example, they insist upon limiting the number of user-configurable variables, which would not make sense if they were only about the basic technologies. In order for their reference interface to be credible, they have to invest resources in usability. The way I see it, the "reference interface" position amounts to a committment to an end-user product, even if they don't realize or admit it.
On top of this, Mozilla already has all the visibility in the free software and web development communities. If Mozilla refuses to provide an end-user product, it will mostly create user confusion. Mozilla has all the developers. Mozilla has all the infrastructure. It only makes sense for Mozilla to do the last 10% and provide an end-user product. Maybe someday beonix or galeon or someone else will overcome this barrier (just as GTK and QT have finally displaced athena as free widget sets for X), but it will take a long time.
Of course, in some markets, vanilla Mozilla won't be the king. Among Joe PC, it will a Netscape or AOL branded version. Users of embedded systems will get whatever modified version their manufacturer included. But even the popular computer press reviews Mozilla, so the message that it is not for end-users doesn't seem to have gotten through. And among the slashdot demographic, Mozilla is it. Let's face it: how many of us will download Mozilla 1.0 to "test" it? Most of us want to use it! Mozilla is already a great end-user browser, and will keep getting better.
The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
I can put one together myself, but I'm not certian what the best (most easily understood) directory structure would be... Perhaps something like this:
- Root
- Linux
- Suse
- Redhat
- ...
- BSD
- FreeBSD
- NetBSD
- ...
- Windows
- Source
- DOCS
I'd like to have something burnable by next Wednesday for the Ann Arbor Destroyed by Mozilla party...-Adam
June 5th 2002 - Mozilla 1.0 Released
Roughly, about 4.5 years.
NOTE: you can't start the profile manager unless Mozilla is fully shut down.
http://rocknerd.co.uk