Domain: mozilla.org
Stories and comments across the archive that link to mozilla.org.
Comments · 17,579
-
Mozilla 1.0 was not delayed
I drew the roadmap.
Mozilla 1.0's ship date has been the same for around 3 years now: "When It's Ready".
When I drew the first roadmap which mentioned a 1.0 release [2], I placed it "in the future", faded out and labelled "if we're lucky". The accompanying text explained that Mozilla 1.0 would be released "when it is ready". When I next changed the roadmap significantly [4], it was to add in another milestone (0.8.1) which had been requested by groups who use the Mozilla codebase in their projects (like Nautlius and AOL). So far, nothing too serious.
The next big change [5] was to simply move the roadmap along a bit so that there was more room. Mozilla 1.0 was still a faded out, but I also took the opportunity to move it along a bit too, thus keeping it at the end of the roadmap. The release date for 1.0 was not changed, it was still "when it's ready".
However, when that roadmap diagram was published, I discovered that I had previously a undiscovered power among the Slashdot community! People were outraged that the faded lines had been moved! The text hadn't changed, the release date hadn't changed, but the image was adjusted a bit and this is clearly what matters!
Wary of this amazing power, when I made my next update to the roadmap image [6] I was very careful about making the release date of the Mozilla 1.0 product extremely clear: the branch is labelled "Mozilla 1.0 (when it is ready)". I figured that would prevent another outburst from my fans.
Clearly not! Both RootPrompt and Slashdot have me as their top article! My power remains untamed! Woohoo!
:-DThe roadmap images:
- http://mozilla.org/roadmap-images/branching.gif
- http://mozilla.org/roadmap-images/branching-15-De
c -2000.png - http://mozilla.org/roadmap-images/branching-13-Fe
b -2001.png - http://mozilla.org/roadmap-images/branching-01-Ma
r -2001.png - http://mozilla.org/roadmap-images/branching-05-Ap
r -2001.png - http://mozilla.org/roadmap-images/branching-09-Ma
y -2001.png
So when will Mozilla 1.0 be ready? We have a definition document.
-
Mozilla 1.0 was not delayed
I drew the roadmap.
Mozilla 1.0's ship date has been the same for around 3 years now: "When It's Ready".
When I drew the first roadmap which mentioned a 1.0 release [2], I placed it "in the future", faded out and labelled "if we're lucky". The accompanying text explained that Mozilla 1.0 would be released "when it is ready". When I next changed the roadmap significantly [4], it was to add in another milestone (0.8.1) which had been requested by groups who use the Mozilla codebase in their projects (like Nautlius and AOL). So far, nothing too serious.
The next big change [5] was to simply move the roadmap along a bit so that there was more room. Mozilla 1.0 was still a faded out, but I also took the opportunity to move it along a bit too, thus keeping it at the end of the roadmap. The release date for 1.0 was not changed, it was still "when it's ready".
However, when that roadmap diagram was published, I discovered that I had previously a undiscovered power among the Slashdot community! People were outraged that the faded lines had been moved! The text hadn't changed, the release date hadn't changed, but the image was adjusted a bit and this is clearly what matters!
Wary of this amazing power, when I made my next update to the roadmap image [6] I was very careful about making the release date of the Mozilla 1.0 product extremely clear: the branch is labelled "Mozilla 1.0 (when it is ready)". I figured that would prevent another outburst from my fans.
Clearly not! Both RootPrompt and Slashdot have me as their top article! My power remains untamed! Woohoo!
:-DThe roadmap images:
- http://mozilla.org/roadmap-images/branching.gif
- http://mozilla.org/roadmap-images/branching-15-De
c -2000.png - http://mozilla.org/roadmap-images/branching-13-Fe
b -2001.png - http://mozilla.org/roadmap-images/branching-01-Ma
r -2001.png - http://mozilla.org/roadmap-images/branching-05-Ap
r -2001.png - http://mozilla.org/roadmap-images/branching-09-Ma
y -2001.png
So when will Mozilla 1.0 be ready? We have a definition document.
-
Mozilla 1.0 was not delayed
I drew the roadmap.
Mozilla 1.0's ship date has been the same for around 3 years now: "When It's Ready".
When I drew the first roadmap which mentioned a 1.0 release [2], I placed it "in the future", faded out and labelled "if we're lucky". The accompanying text explained that Mozilla 1.0 would be released "when it is ready". When I next changed the roadmap significantly [4], it was to add in another milestone (0.8.1) which had been requested by groups who use the Mozilla codebase in their projects (like Nautlius and AOL). So far, nothing too serious.
The next big change [5] was to simply move the roadmap along a bit so that there was more room. Mozilla 1.0 was still a faded out, but I also took the opportunity to move it along a bit too, thus keeping it at the end of the roadmap. The release date for 1.0 was not changed, it was still "when it's ready".
However, when that roadmap diagram was published, I discovered that I had previously a undiscovered power among the Slashdot community! People were outraged that the faded lines had been moved! The text hadn't changed, the release date hadn't changed, but the image was adjusted a bit and this is clearly what matters!
Wary of this amazing power, when I made my next update to the roadmap image [6] I was very careful about making the release date of the Mozilla 1.0 product extremely clear: the branch is labelled "Mozilla 1.0 (when it is ready)". I figured that would prevent another outburst from my fans.
Clearly not! Both RootPrompt and Slashdot have me as their top article! My power remains untamed! Woohoo!
:-DThe roadmap images:
- http://mozilla.org/roadmap-images/branching.gif
- http://mozilla.org/roadmap-images/branching-15-De
c -2000.png - http://mozilla.org/roadmap-images/branching-13-Fe
b -2001.png - http://mozilla.org/roadmap-images/branching-01-Ma
r -2001.png - http://mozilla.org/roadmap-images/branching-05-Ap
r -2001.png - http://mozilla.org/roadmap-images/branching-09-Ma
y -2001.png
So when will Mozilla 1.0 be ready? We have a definition document.
-
Instead of flaming each other, consider this...
1) Whats the rush for AOL to release the new browser now that AOL is going with IE? None.
2) The release schedule in actuality has not changed. Go to mozillaquest and compare the two graphics for yourself - they only moved the 'X' further along and pushed the 1.0 grey branch down - the point releases have not been moved, hence, the production schedule remains the same.
3) I use mozilla day-in-and-day-out - i'm using it right now. It beats the sh*t out of IE. Why? Because if we have no other choice, and we all had to use IE, as soon as M$ sees no more competition, they will stop producing the crappy thing for other platforms. Oh, sorry Steve Jobs, we decided that Mac's are too difficult to support, bye. Then what would us Linux, BeOS, Sun, Amiga, HP, and others do? Stop using the web. Riiiiiiiiight. Time to swtich to Windows! What else has M$ showed over the years other than the ability to twist peoples arms and make them use Windows?
4) For the love of God, people - quit frickin' cutting our own throats. Mozilla is our ONLY major OpenSource platform for web applications. (Which, hopefully, some of you more intelligent slashdotters realise is the future of the web.) If you dont like it, download it and try it again - like now, today. If you still dont like it - SHUT UP! We could kick each other in the teeth day after day about how Redhat is more secure than LinuxPPC, or how Mandrake is better for newbies, ow what have you, but what does that accomplish? NOTHING. The best thing you could ever hopw of your competition is that they attack each other - united we stand folks, divided we fall.
Mozilla - you're soaking in it. -
Better URLThe "tree management diagram" is also known as the "roadmap" and is located at
http://www.mozilla.org/roadmap.html
and it was updated to the current state three weeks ago (i.e. this is not news). It's done when it's done. In the meantime, the milestone releases (0.9, 0.9.1 soon) are very very good. Nightly builds are bit more risky but addin/fix/improve features and performance.
-
Can we trust that projection?That source tree (scroll down a bit) says that in a worst-case scenario, we might only be at 0.9.6 or 0.9.7 by the end of Q4 2001.
Just curious, but considering how delayed the thing is already, why should we believe their optimistic best-case projections? Sorry if this sounds like trolling, but I'm genuinely curious.
-
Re:maybe it's because AOL wants a decent browser
the latest version of MSIE does not crash
Are you sure about this? I've had IE crash a fair amount of times recently. Of course, being a web developer, I also know what kind of stuff will make almost any browser crash. I just love getting the "Internet Explorer has crashed" dialog box.
is stable, stable, stable
You haven't used Mozilla 0.9 yet. That's all I can say.
does not waste resources with stupid themable interface
I don't see it as a waste of resources -- it has to load a set of pixmaps/bmps/etc whether it's using a single "theme" that's part of the browser in the first place (see MSIE, Netscape 4.x), or loading multiple "themes" out of files (see WinAmp, XMMS, etc).
does not have major parts of the browser written in java script
Just the UI.
does not require 128 megs of ram to run
Mozilla-0.8.1 embedded on a Pentium/120 with 48M ram. It flew. Repeat that please?
does not include stupidity such as AIM clients and IRC clients
Both of which are fully optional if I'm not mistaken? Some people like doing everything out of one interface. Live with it.
at some point mozilla may become a better browser, but right now it is not. it is behind.
Try it before you knock it. Sure, it has it's bugs, but so does MSIE.
The primary reason that I see for AOL including MSIE over Mozilla (which, BTW, has been stated many times over on this article by other people) is for getting their icon on the WinXP desktop. It's all a marketing ploy to get people to sign up with them -- if you didn't know anything about the internet or anything else, but found an AOL icon sitting on your desktop, would you be more likely to call your local ISP, install the insert-service-provider-name-here cd that showed up in your mail the day before, or use what was already there? Considering that my mother used AOL for a while.. I think it's that much more likely that they'll use what already exists on their system before installing something else or getting online with a real ISP.
Just my 0.02.
-
Re:Mozilla's usable now
SSL's been working in Mozilla for a damn long time now. Make sure you're downloading the right build (some don't come with the PSM(==Personal Security Manager) installed -- but even then you can do it seperately by just grabbing psm.xpi from netscape's or mozilla's ftp sites. I generally grab the build labeled mozilla-i686-pc-linux-gnu-sea.tar.gz
!!Damn I can't believe I just typed that url from memory, and I think it's right too. -
Re:Not sure that this is news exactly...
IE has one major feature that Netscape still doesn't even come close to approaching -- an API that can be used to make a custom browser (which is just a shell over the HTML/Script parsing engine that offers most of the functions of a web browser).
Um. Perhaps you haven't been paying attention? Mozilla (and therefore Netscape 6+) is easily embedded.
-
Re:Not sure that this is news exactly...
IE has one major feature that Netscape still doesn't even come close to approaching -- an API that can be used to make a custom browser (which is just a shell over the HTML/Script parsing engine that offers most of the functions of a web browser).
Um. Perhaps you haven't been paying attention? Mozilla (and therefore Netscape 6+) is easily embedded.
-
Re:Not sure that this is news exactly...
IE has one major feature that Netscape still doesn't even come close to approaching -- an API that can be used to make a custom browser (which is just a shell over the HTML/Script parsing engine that offers most of the functions of a web browser).
-
tinderboxThe Mozilla project uses tinderbox. It comes in version 1 and 2 flavours, and is nowhere near mature (version 1 is more mature, I believe), but it is an open source framework that already exists. It is a tool for automating testing and reporting results. For running test cases you need something else, like DejaGNU.
You might also find that a lot of projects are using lighterweight scripts to automate testing. Since the software available isn't mature, a quick custom solution written in a scripting language (shell or Perl are good choices) might be a good solution.
-
Re:Death's Road.
OK, why isn't Netscape keeping up with the Mozilla release schedule? Because they never wanted to release 6.0. As somebody else said above, they did it because of market pressure. Look at the latest roadmap. It even has a an X to mark the spot. You'll see that little X where they mention their current progress, how a bunch of new code has been added, (which are heavily demanded features or for performance improvements) and how the source tree is in flames as a result. Go a little farther and you will see the the blue lines marked 'recommended beta branch time' and 'vendor branches as required'. Those will probably be the Netscape 6.5 beta releases. Mozilla 0.9.1 and 0.9.3, after the addition of silly Netscape customizations like a shop button, will become the Netscape betas and eventually the release version.
It isn't worth it for Netscape to track the Mozilla milestones because the effort to recustomize each time would take up developer time that is better spent on the common source base. Those Netscape-brand customization branches would cause bugs that have to be fixed separately without adding to the end product. Understand this, Netscape 6.0(1) was a 'feature-complete' pre-beta/technology preview. I'm sure that Netscape knows it was pre-beta quality. It was put out there under pressure from journalists and standards advocates who immediately proceeded to about-face and blast the result. So Netscape decided that if that's the thanks they get, they'll release the next version when its ready. What did you expect when Netscape got slammed for doing what everybody else claimed they wanted?
The developers probably told management "We told you it wasn't ready!" and management certainly knew it wasn't ready, but they needed to keep up the perception that they were listening to the user base.
On the other hand, if Netscape is being kept alive by AOL to keep MS honest, Netscape 6.X is only effective as FUD if it is perceived to be a viable threat and not complete vapourware. Until the Netscape 6.X release, crappy as it was, the whole project was in serious danger of being perceived as vapourware and giving MS an effective browser monopoly. At that point it becomes ineffective for use as FUD by AOL and their funding might have dried up. All that bad publicity from NS6 meant that at least people were still talking about Netscape instead of forgetting about it. If NS 6.x was the price to keep Mozilla afloat to get to this point, then it was worth it. It's too bad they couldn't call it Technology Preview 2 instead of NS 6.0 -
mozilla as multi-user package
afaik, bug 42184 is still unresolved. As a sysadmin, I can't really take mozilla seriously when its release notes suggest installing it separately for each user who wants to run it.
-
mozilla as multi-user package
afaik, bug 42184 is still unresolved. As a sysadmin, I can't really take mozilla seriously when its release notes suggest installing it separately for each user who wants to run it.
-
Re:Thanks for talking out of your ass
Those sound like good ideas. I'm not sure if they've been suggested or not, but if you want to know, you can head over to bugzilla and check. If they're not there, you can file them as request for enhancements (rfe).
Their current work load is focused on finishing features/bugs for NS6.5, but once work on 7.0 starts (end of the summer, last I checked), there will be *lots* of room for feature work.
-- -
Re:I've been running nightlies regularly
Other than that, recent changes in how pages are built make everything seem a lot smoother and faster. I forget what they called the one fix... it had a funny description, but the upshot was that you can now click on things on an "outgoing" page if your new page hasn't loaded yet. For us impatient browsers who give up on crappy-loading sites, that one was a real breakthrough!
That was probably bug 76495, "We tear down the world before having anything to replace it with."
Unfortunately, bug 78680, "if a page is loading but paint-suppressed, can't interact with old page," hasn't been fixed. So while you can see the old page for a longer time as the new page starts to load, you can't necessarily click on other parts of the old page. -
Re:I've been running nightlies regularly
Other than that, recent changes in how pages are built make everything seem a lot smoother and faster. I forget what they called the one fix... it had a funny description, but the upshot was that you can now click on things on an "outgoing" page if your new page hasn't loaded yet. For us impatient browsers who give up on crappy-loading sites, that one was a real breakthrough!
That was probably bug 76495, "We tear down the world before having anything to replace it with."
Unfortunately, bug 78680, "if a page is loading but paint-suppressed, can't interact with old page," hasn't been fixed. So while you can see the old page for a longer time as the new page starts to load, you can't necessarily click on other parts of the old page. -
Who needs it? I do!
Not for the browser... no, I can easily live in my galeon-ized world quite happily without the netscape browser. Unfortunately, I still need digital signing/encrypting ability for my mail, and my company has adopted X509 (verisign) certs for this. As all inter-company mail must be encrypted, I can't get around this.
Yes, I tried to convince them to use pgp/gpg, but the lack of integration with netscape and other (windows) mail clients made that no happen :( I *really* wanted it to.
There is alread a bug about this in the bugzilla database, but it looks like they aren't going to be able to get it in by 1.0 :( Yes, I'd love to help them instead of just bitching, and I would if I had any experience coding this part of the system. -
Re:Mozilla?
I disagree. I also run Windows as my primary OS; IE is by far the slowest browser I've used. For raw speed, nothing right now beats Opera. Although supposedly it sticks to the standards to most, a lot of pages dont look perfect in it. Mozilla is definitely getting MUCH better. I'm actually using it right now: much faster than IE6.0 in just about everything. These are my experiences; your mileage may vary. As an aside, does Slashdot use http/1.1 compression? One of my favorite game news sites now uses it, and everything loads perceptibly faster...
-
Jamie Zawinski, is -I'm sure- Thrilled about this
I'm sure Jamie Zawinskiis thrilled about this. It seemed that he took it as a personal failure that Mozilla.org didn't take off in it's first year of operation. In the last 6 months it seems to have been holding it's own and here's one of the proofs of that theory. Keep up the good work guys.
--CTH
-- -
Re:NetscapeThe OS/2 version of Mozilla 0.9 can be downloaded from ftp://ftp.mozilla.org/pub/mozilla/releases/mozill
a 0.9/mozilla-i386-pcos2-vacpp-0.9.zip. In other words, you're a moron.BTW, feel free to ask the Mozilla team what they think about the OS/2 programmers they work with.
--
Lord Nimon -
Re:What we really need
There are a couple of systems that already exist. XwingML builds Java Swing interfaces from an XML specification. XUL is a similar XML-based markup supported by Mozilla. XForms is the W3C's draft standard for the next generation of web forms.
Most particularly you may want to look at UIML, which is intended as a cross-(viewing-)platform markup, supporting PCs, PDAs, etc. There is a Java viewer, and the new version seems to have some renderers for WML and HTML, but a text renderer should be possibe (if not already available).
There are several other lesser-known XML-to-GUI toolkits, such as KUIL and AUIT. Most of these are implemented in Java and map the Java Swing classes into XML (as with XwingML).
-
Re:PSM 2.0
It works fine for me. If you're having problems, why not report a bug?
-
Re:LDAP support?
LDAP support is going to be in 0.9.1.
I believe the UI for it was checked in a couple nights ago but don't quote me on that.
Ah yes according to this Link:
5-7-1: LDAP autocomplete feature checkins happened on friday. In non-installer builds (ie .zip, .tar.gz), LDAP autocomplete works, modulo bugs, if you set the appropriate preferences.
No known regressions. Master tracking bug number for LDAP Autocomplete: 17880. The only remaining work before closing this "landing" out is to get the appropriate installer packaging tweaks checked in. Should happen today. -
Re:Not True on Linux
There should be a nice performance gain when they move to gcc 2.95.3 and start using -O2 to optimize as well.
See http://bugzilla.mozilla.org/show_bug.cgi?id=53486 for details.
The only reason this hasn't happened yet is they didn't want to introduce potential compiler and optimization issues right before the .9 release. -
LDAP support?It's nice to see this browser is coming along so nicely! Quick question: Does anyone know when LDAP support will be offered in the Mail/News client? Until this support is included I cannot see a wide spread adoption from Netscape Messenger users.
Reading the bugzilla report it doesn't seem like anyone is taking this problem that seriously...
-
Please use talkback builds.Please, please, please, use our talkback builds on Windows, Macintosh and Linux. Using talkback builds gives us more crash data so common crash bugs can be quickly identified and fixed. Yes, people really do look at this stuff. This is an incredibly easy way to report bugs. You don't need a bugzilla account, you don't need to write coherent english sentences and for a change, filing DUPLICATES IS GOOD!
Here's a sample crash analysis page. Watch out, this page is 2+ MB.
-
Please use talkback builds.Please, please, please, use our talkback builds on Windows, Macintosh and Linux. Using talkback builds gives us more crash data so common crash bugs can be quickly identified and fixed. Yes, people really do look at this stuff. This is an incredibly easy way to report bugs. You don't need a bugzilla account, you don't need to write coherent english sentences and for a change, filing DUPLICATES IS GOOD!
Here's a sample crash analysis page. Watch out, this page is 2+ MB.
-
Please use talkback builds.Please, please, please, use our talkback builds on Windows, Macintosh and Linux. Using talkback builds gives us more crash data so common crash bugs can be quickly identified and fixed. Yes, people really do look at this stuff. This is an incredibly easy way to report bugs. You don't need a bugzilla account, you don't need to write coherent english sentences and for a change, filing DUPLICATES IS GOOD!
Here's a sample crash analysis page. Watch out, this page is 2+ MB.
-
Please use talkback builds.Please, please, please, use our talkback builds on Windows, Macintosh and Linux. Using talkback builds gives us more crash data so common crash bugs can be quickly identified and fixed. Yes, people really do look at this stuff. This is an incredibly easy way to report bugs. You don't need a bugzilla account, you don't need to write coherent english sentences and for a change, filing DUPLICATES IS GOOD!
Here's a sample crash analysis page. Watch out, this page is 2+ MB.
-
Re:Konq
Konqueror's great, but it can't handle the Bugzilla query page.
-
Re:Interruption Based Ads
CoachS said:
The model that's even more maddening to me are sites that spawn additional browsers without asking me. I hate clicking to a site only to have 3 more browser windows pop up with surveys and videos and ads -- even worse when you're trying to leave the site to have multiple, persistent, ads flung at you without recourse. This kind of browser-jacking is a fast way to get on my list of sites I'll never come back to.
If you use mozilla (0.8+), including the following in your prefs.js will help:
user_pref("capability.policy.default.windowinter na l.open","noAccess");
More on this in the mozilla 0.8 release notes. -
Gestures for Mozilla :)
I've filed an RFE bug report for mouse gestures in Mozilla. If you'd like to see mouse gestures in Mozilla, please vote for this bug. Of course, you need a Mozilla account to vote on bugs, but you can easily create an account if you don't have one.
Alex Bischoff
--- -
Gestures for Mozilla :)
I've filed an RFE bug report for mouse gestures in Mozilla. If you'd like to see mouse gestures in Mozilla, please vote for this bug. Of course, you need a Mozilla account to vote on bugs, but you can easily create an account if you don't have one.
Alex Bischoff
--- -
Gestures for Mozilla :)
I've filed an RFE bug report for mouse gestures in Mozilla. If you'd like to see mouse gestures in Mozilla, please vote for this bug. Of course, you need a Mozilla account to vote on bugs, but you can easily create an account if you don't have one.
Alex Bischoff
--- -
Re:Good question in "talkbacks"
It appears that the real problem may be with how gcc and mozilla are interacting. Please see this status update, in which it states that gcc is generating code that is twice as large as what Visual C++ is generating. If Linux builds are executing twice as many instructions, of course the Windows builds will be faster. Further follow-ups don't show much progress other than that switching from egcs to gcc 2.95.2 reduced size by about 5%.
Unfortunately, using gcc 2.95.2 requires a libc upgrade. I just installed the gcc 3.0 3/20/01 snapshot and am going to try a build tonight to see if it makes much difference.
Since pavlov was moved to help out with libpr0n, I haven't been seeing many updates about general Linux performance. Back in November thru early January, this was one of the main things the Footprint team was working on. pavlov seemed to be one of the most knowledgeable guys in the area and there were several people assigned to it. It seems they all got pulled elsewhere.
To really make Mozilla work well in unix, they need to put the focus back on speed and also take a look at the memory leaks that plague the linux version. After browsing for a few hours, Mozilla tends to swell up from around 20 megs of ram to 50 or 60. They had some graphs profiling this problem, but those seem to have stopped being updated as well.
On the whole, I find Mozilla pretty darn useable at 0.8.1. I run it on Linux and FreeBSD (under linux emulation so I can use the flash plugin) and it barely ever crashes -even when subjected to the massive javascript porn popup stress test. -
Re:Good question in "talkbacks"
It appears that the real problem may be with how gcc and mozilla are interacting. Please see this status update, in which it states that gcc is generating code that is twice as large as what Visual C++ is generating. If Linux builds are executing twice as many instructions, of course the Windows builds will be faster. Further follow-ups don't show much progress other than that switching from egcs to gcc 2.95.2 reduced size by about 5%.
Unfortunately, using gcc 2.95.2 requires a libc upgrade. I just installed the gcc 3.0 3/20/01 snapshot and am going to try a build tonight to see if it makes much difference.
Since pavlov was moved to help out with libpr0n, I haven't been seeing many updates about general Linux performance. Back in November thru early January, this was one of the main things the Footprint team was working on. pavlov seemed to be one of the most knowledgeable guys in the area and there were several people assigned to it. It seems they all got pulled elsewhere.
To really make Mozilla work well in unix, they need to put the focus back on speed and also take a look at the memory leaks that plague the linux version. After browsing for a few hours, Mozilla tends to swell up from around 20 megs of ram to 50 or 60. They had some graphs profiling this problem, but those seem to have stopped being updated as well.
On the whole, I find Mozilla pretty darn useable at 0.8.1. I run it on Linux and FreeBSD (under linux emulation so I can use the flash plugin) and it barely ever crashes -even when subjected to the massive javascript porn popup stress test. -
Re:Good question in "talkbacks"
It appears that the real problem may be with how gcc and mozilla are interacting. Please see this status update, in which it states that gcc is generating code that is twice as large as what Visual C++ is generating. If Linux builds are executing twice as many instructions, of course the Windows builds will be faster. Further follow-ups don't show much progress other than that switching from egcs to gcc 2.95.2 reduced size by about 5%.
Unfortunately, using gcc 2.95.2 requires a libc upgrade. I just installed the gcc 3.0 3/20/01 snapshot and am going to try a build tonight to see if it makes much difference.
Since pavlov was moved to help out with libpr0n, I haven't been seeing many updates about general Linux performance. Back in November thru early January, this was one of the main things the Footprint team was working on. pavlov seemed to be one of the most knowledgeable guys in the area and there were several people assigned to it. It seems they all got pulled elsewhere.
To really make Mozilla work well in unix, they need to put the focus back on speed and also take a look at the memory leaks that plague the linux version. After browsing for a few hours, Mozilla tends to swell up from around 20 megs of ram to 50 or 60. They had some graphs profiling this problem, but those seem to have stopped being updated as well.
On the whole, I find Mozilla pretty darn useable at 0.8.1. I run it on Linux and FreeBSD (under linux emulation so I can use the flash plugin) and it barely ever crashes -even when subjected to the massive javascript porn popup stress test. -
Re:i am confused...Well, the *n?x port is dependent on gtk+. It was already dependent on a toolkit; this port simply makes it dependent on a different toolkit.
-
Re:rotten to the core
- "Fleet.Ford.com has been designed for viewing with Netscape 4.x and Microsoft Internet Explorer 4.x to 5.x. All the features of this site are not viewable with the browser that you are currently using. You may download a supported version from Netscape or Microsoft."
Alex Bischoff
--- -
Re:Compared to IE5.5 it's still pathetic.
Mozilla is now 0.8.1
the 0.8.1 release not appear in slashdot.
:(
Related Mozilla bugs = http://bugzilla.mozilla.org/show_bug.cgi?id=73658
-
ie development
IE 1.0 was released with Windows 95, in August of 1995. From all reasonable accounts, IE wasn't very good until version 5, which was released March 1999. That's three and a half years.
The Mozilla project started with Gecko in Oct 1998. Even if you start with the less-charitable date of April 1998 (when the Communicator source was opened -- and turned out to not actually be very useful), it's still only three years 'til right now. (And remember, IE didn't start from scratch -- they began with the Spyglass Mosaic codebase.)
If you look at the current Mozilla roadmap, even the "if we're unlucky" plan calls for 1.0 to be out by Q3 of this year -- plenty of time to beat IE 5.0 by your suggested metric. -
Re:And ��
You may wish to try one of the recent builds of Mozilla. Using a recent build, I've posted many comments to Slashdot (including this one) without problem.
Alex Bischoff
--- -
Re:And ��
You may wish to try one of the recent builds of Mozilla. Using a recent build, I've posted many comments to Slashdot (including this one) without problem.
Alex Bischoff
--- -
Trenchant InsightI would have much rather had to wait a few months and had a product that worked nearly flawlessly, so that I could recommend it to my friends, rather than be forced to recommend a winCE powered, or palmOS powered device. It's really a shame that market pressure ruins so many good ideas.
<RANT> Oh what a steaming pile of self-righteous crap! I'm sorry to have to inform you that in the private sector these days, virtually everything is always shoved out the door before the engineers say it's done. The fact is we all love to perfect our creations, but time (or VC funding) waits for no man, and the suits do indeed have a job -- get the product out there and start pulling in revenue before all the cash is gone. </RANT>
Take a look at Mozilla at any time over the past two years -- it always seems like they just need a couple more months and it'll be perfect. Netscape bit the bullet last fall and shoved NS6 out the door -- now it's four months later and Mozilla just issued a new roadmap that delays '1.0' until Q3. Should Netscape have waited "a few months"?
Things get done in this world by people who design, execute, tweak it up a bit, shove it out the door, evaluate, re-prioritize and do it all again. "Works flawlessly"? Ha! Product design is asymptotic -- you'll get closer and closer, but you're never really THERE, and so someone has to stick their neck out and say "enough already". Companies run by engineers do NOT necessarily succeed -- you need a balance of technical and fiscal considerations in any decision.
Sounds like Agenda's got problems, but as has been stated elsewhere, it's too early to make a judgement on that.
- Master Of The Obvious
-
First Java, then XUL, then .NET, then Reef...Now Curl.
Yesterday, Eazel just announced Reef, yet another attempt to do the same thing Microsoft announced with
.NET which is similar to Dave Hyatt's XUL (+CSS+JS) for the Mozilla project which promised to do what Java was supposed to do.All this so I can subscribe to my word processor on a monthly basis?
Kinda depressing.
Seriously, can't we all get together and decide on a single system without everyone going off doing their own thing?
Answer: No.
------------------- -
ActiveX/OLE the ultimate component model???
Meanwhile on Windows, you've got a single model, COM.
Now, tell me why a platform with maybe at best a 2% desktop marketshare needs 4 different ways of component embedding and a platform with 90% marketshare can get away with one.
Microsoft's COM itself is not too bad as a substrate, which may explain why Mozilla chose to emulate the COM model with XPCOM. However, the actual embedding of user-interface components within Windows applications depends on ActiveX, a broad collection of COM interfaces, and implementations thereof, which integrate with the underlying Windows API (Win32).
Almost anyone who has done any development with ActiveX should be able to tell you that this is not the ultimate component embedding model. Nor, for that matter, is Win32 the ultimate OS API. I should add that these are both serious understatements.
I think it's far more likely that future user interfaces will use a model more along the lines of HTML or Display Postscript, i.e. a more client/server based approach, although clearly neither of those two technologies in their current form can fully address the problem.
It's incredibly unlikely that Microsoft will be the one to provide the next rational component model - its entire history demonstrates that it doesn't have what it takes to truly innovate, no matter how many of its billions it throws at people researching Bayes networks and first order phase transitions.
If anything, Microsoft's ability to innovate is probably declining as market forces begin to work against it - IOW, it may have peaked. Perhaps its research division will eventually begin paying off in the way that IBM's does, but so far there's no indication that it will do so in the software arena.
So, while I don't happen to think Gnome or KDE will be the future of components either, I do think that the future is far more likely to come from an unexpected direction than from Microsoft. HTML and the web are a perfect example of this; Java is another, with Microsoft now vaporing
.NET to catch up.The bottom line is that we're not at a stage where it's technically valid to say "OK, all the user interface development problems have been solved and we can all standardize on one thing". We need alternatives, and there's no place better to try out different approaches than on a free, open OS that doesn't restrict competition and innovation with a closed API.
-
We still have a LOT of WORK to do!
An operating system is not only the kernel and a bunch of device drivers! We didn't even start the most important project of them all: consolidating our manpower and our technologies. We could really use a component object model. The good news is: we have that technology. The bad news is we are working on more than one.. XPCom part of the Mozilla web browser project and ORBit part of the Gnome Desktop project. Speaking of desktops, like Doug said, we are working on two competing projects, Gnome and KDE. We already have all the technologies Doug thinks put Microsoft ahead in the game. Mainframe / AS400 connectivity? Linux-SNA. A kick-ass web browser? Mozilla vs. Internet Explorer. Word processor, spread-sheet, Business presentations? Star-Office. I could go on and on but I guess you get the picture. What we have to do now is to consolidate all that into a coherent system.. I want to be able to manipulate Star-Office spread-sheets using a system-wide scripting language (how about perl? python?..?).. I want to be able to embed that spread-sheet into any application, not only into Star-Office's word processor (XPCom? ORBit?) I want to be able to use the same printer driver from Star-Office and any other application on the system (anybody working on a printing subsystem for X? Or do we put it into GTK's GDK?).. There's still a lot of work for us to do before we can really kick their asses on the desktop. I'm looking forward to both.
-
We still have a LOT of WORK to do!
An operating system is not only the kernel and a bunch of device drivers! We didn't even start the most important project of them all: consolidating our manpower and our technologies. We could really use a component object model. The good news is: we have that technology. The bad news is we are working on more than one.. XPCom part of the Mozilla web browser project and ORBit part of the Gnome Desktop project. Speaking of desktops, like Doug said, we are working on two competing projects, Gnome and KDE. We already have all the technologies Doug thinks put Microsoft ahead in the game. Mainframe / AS400 connectivity? Linux-SNA. A kick-ass web browser? Mozilla vs. Internet Explorer. Word processor, spread-sheet, Business presentations? Star-Office. I could go on and on but I guess you get the picture. What we have to do now is to consolidate all that into a coherent system.. I want to be able to manipulate Star-Office spread-sheets using a system-wide scripting language (how about perl? python?..?).. I want to be able to embed that spread-sheet into any application, not only into Star-Office's word processor (XPCom? ORBit?) I want to be able to use the same printer driver from Star-Office and any other application on the system (anybody working on a printing subsystem for X? Or do we put it into GTK's GDK?).. There's still a lot of work for us to do before we can really kick their asses on the desktop. I'm looking forward to both.