Mozilla 1.7 Beta Is Faster And Smaller
ccady writes "Mozilla 1.7 beta is out. Not too many new features, but "Mozilla 1.7 size and performance have improved dramatically with this release. When compared to Mozilla 1.6, Mozilla 1.7 Beta is 7% faster at startup, is 8% faster at window open time, has 9% faster pageloading times, and is 5% smaller in binary size." I'll be downloading it."
Go Go Mozilla!
You know where you are? You're in the $PATH, baby. You're gonna get executed!
Wow, I got here first using 1.6. Looks like some people will need 1.7 to get here faster next time
This is why I stopped using Netscape: each version was much larger, much slower, and much less reliable.
How can something with the same kernel, and the same ancestry go the other way: Mozilla actually improves as it evolves.
On the one hand, the dodo. On the other hand, the road-runner.
When was the last time IE was updated????
It's either on the beat or off the beat, it's that easy.
I moderate therefore I rule!
--
I hear its got 20% more zilla too!
Statistics than you'll ever need...
"Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
The next service pack of Internet Explorer plans to have longer load times, more crashes, and open a few more exploits into a Windows system.
Modzilla keeps getting better all the time.
Mozilla has a small marketshare, practically no one uses it, and finally Long Live IE!
True.
Intelligence also has a small marketshare...
Treehugger? Treehugger... Treehugger!
I seriously doubt that a performance improvement 10% is even noticeable to the user. It's great that Mozilla is trying to catch up with fast browse-only alternatives like Safari, Konqueror and also the Gecko-based browsers, but you can't seriously speak of 'dramatic' improvements.
yes, firefox is nothing without the underlying Gecko engine. Shortly firefox will branch on the Mozilla 1.7 branch, it is very likely that Mozilla 1.8-1.9 will have much faster page rendering that Firefox 1.0. See bugzilla for the bugs targetted for 1.8alpha
I got here so fast using konqueror that the server hadn't even recorded my post by the time I left.
When compared to Mozilla 1.6, Lynx is 99% faster at startup, 99% faster at window open time, has 50% faster pageloading times, and is 90% smaller in binary size.
In all seriousness, it's easy to improve figures like this just by removing features.
Tarsnap: Online backups for the truly paranoid
The fastest speed up is not even 10%. That's about an extra 0.01 tits/second. Want more speedup than that.
Engineering is the art of compromise.
I'm really impressed, and very much appreciative, of the amount of effort the Mozilla team has put forth over the years. I switched to Mozilla some 4 or 5 years ago, and haven't looked back since. The rapidity of development is truly astounding -- thanks girls and guys!
That having been said, I've been dissapointed with the latest iteration of the Mozilla browser. I've found 1.6 to be rather slow (autocomplete lags, for example), bug prone and (if I'm correct) java support is still on the fritz.
I'm liable to switch over to FireFox (or whatever it's called this week), except the Preference Toolbar (on which I'm hooked like a crack addiction) still does not function in this stripped down version of the Moz browser.
Anyway, I look forward to this newest version; really, I just wanted to express, in this post, my thanks for the effort put forth by the whole Moz team.
Regards,
=pararox=
Firefox will get the speed improvements, but since Firefox is already smaller and uses less, it won't be as significant (I think it is 3%?).
They basically rewrote the string implementation and it is "better faster stronger" than before.
So yeah, Firefox 0.9 will get a speed improvement too. (You can also grab a nightly. They have the improvements -- and more bugs.)
P.S. Also new in Mozilla 1.6 is the ability to block websites from hijacking your context menu (right click menu) in the browser. Yay!
Get Firefox!
How can firefox render better, it has the same rendering engine as Mozilla, are you comparing the same Mozilla version as the one which firefox is based on
e.g, Mozilla 1.6-Firefox 0.8
Mozilla 1.5-Firefox 0.7
Remeber firefox will branch soon from the 1.7 release, so far a while, Mozilla (aka Seamonkey) will have rendering fixes/speedups and Firefox won't have it till it returns back to the trunk sometime after 1.0 is released
You're looking at the README for the alpha. Try here instead.
LOAD "SIG",8,1
I just love it and tab-browsing but there is still room for improvement:
A resume feature in the download manager would be a nice start...
It now support's SSO HTTP Authentication using GSSAPI Kerberos. Similiar MS's implementation of SPNEGO in IE. See bug 17578 in bugzilla for more information.
This is compatible with both IIS, and mod_authkerb for apache.
http://sourceforge.net/projects/modauthkerb/
Next the plan is to make kerberos support more general so it can be used for other protocol's like IMAP.
How much faster in comparision to other releases? What I want to know is if Mozilla is progressively getting faster, or is this just to compensate for performance regressions when they went from 1.4 - 1.5, etc.
Of course, it's nice to see they are going in the right direction, but I suppose it will take me a while until I have made up for the time following the link and downloading it (not to speak of the time it cost to post this comment :P) by the increased productivity...
I've been using Mozilla since 0.4 or 0.5, can't quite remember which. It's always been the best, and keeps getting better (tabs anyone?). Every release gets faster, and most get smaller, though not all.
I don't have time to comment my code, the program is late already.
Seeing as Firefox is getting most of the press these days it's important to realise that the full suite is still moving along nicely. They are addressing criticisms well - a redesign of the cookie manager and speed increases are reflective of the fight against bloat and complexity.
And don't forget, changes to the suite are picked up by Firefox since FF is based off the same source tree. So a lot of work here will affect the mini-moz too....
Free iPods - now in the UK!
IE is not expected to see a major revision until Longhorn ships in 2006-2007. It is rumored that the Longhorn version will have tabbed browsing and some kind of pop-up blocking. This would probably be accomplished via the MSN toolbar, which is similar to the Google toolbar but with that *other* search engine.
But the truth is that IE has so much of the market share that revisions don't matter. People tend to use whatever came with their system, even if it is older and came with IE 5. If Microsoft didn't push the patches, quite a few people would be using these older version even now.
BTW, I'm using Firefox.
If my answers frighten you, stop asking scary questions.
Anyone know if memory use has gotten any more efficient? I still find Moz to be a bit high in memory useage. It's not a problem if when it's up and browsing, but if I flipped to another application for awhile, and Moz gets paged out to disk, the delay to switch back to Moz is a little annoying. At least on my relatively slow by today's standards, WinXP box.
On a related note, is it just me, or does Moz get paged out a LOT quicker than many other apps? Is it playing "too" nice somehow?
For detailed information aboutMozilla, read all about it in the wikipedia.
A Megabyte (MB) is now set at 1000 Kilobytes (KB) which is, in turn 1000 bytes. However, most of use still use MB = 1024 KB = 1024 bytes, which is now (officialy?) a Mibibyte (MiB), and Kibibyte (KiB). Confuses me too.
I don't have time to comment my code, the program is late already.
No-one is going to notice a 10% improvement. It is a non-factor. You need to double performance to make a noticeable difference. Granted, if they keep on improving by 10% each release, it will eventually be really good, but don't call a 10% improvement "dramatic" (or whatever the original author called it).
Personally, I like Galeon and Firefox. I just need a web-browser.
social sciences can never use experience to verify their statemen
The latest Galeon is out too. Version 1.3.14. Works with Mozilla 1.4 through 1.7b and trunk. Loads pretty fast too;) For those of you who don't know, galeon is a browser based on mozilla, for gnome-but ofcourse works in other wm's too.
Each firefox release is based on Mozilla. Firefox 0.9 and 1.0 will be based on Mozilla 1.7.
Mozilla will then make Firefox it's primary browser after 1.0, and Thunderbird it's primary mail reader after 1.0. The Mozilla browser you know will still exist as "Mozilla Suite".
On a similiar note - I thought Mozilla was going away in lieu of FireFox and Thunderbird. I stopped using Mozilla long ago for this reason - when are they going to focus on just FireFox and Thunderbird - or are they really? It seems that Most linux distros use Mozilla instead of the seperate clients. This bugs me when I have to install firefox/thunderbird and always makes me ask - "If Mozilla is going away, why do we still use it? Why is it included in the distros?" And ultimately "Why Bother". I know mozilla is a good product, but maintaining a "to be discontinued" product is like cpr on dead people - what's the point? Please enlighten me.
ymmv
After the news is released on Slashdot, it's now 40% slower to download. :D
My blog
Feeding the troll:
You are right. Mozilla's marketshare isn't large. Most Windows users probably don't even know it exists. This doesn't mean they haven't used Mozilla or that Mozilla would be insignificant.
I've seen Mozilla based browsers used in several public web terminals. You will not be able to go to a fair of almost any kind without seeing mozilla used (I've been to quite a few that had little or nothing to do with computers and seen mozilla or a browser using the gecko engine used).
Mozilla will not gain a 95% marketshare today nor tomorrow, but it will gain marketshare. IE will live long, probably a time counted in decades, but Mozilla isn't going away.
I've been following Mozilla closely since milestone 16 and I started using it as my main browser arund version 0.96. Before that it was basically horrible. It was unstable, ate memory like crazy and was too slow for me to use.
Mozilla today is a different beast from the early days:
The most stable (modern) browser I've used (links is the most stable ever)
Best standards support
Getting faster by every release
Getting less resource hungry by every release
The most extendable browser around.
IE will live long but so will Mozilla. Mozilla's marketshare will grow, IE's will probably not. Mozilla is evolving fast, IE is not. Mozilla will always be free, IE might not be. Mozilla will be developed as long as anyone wants to do it or has the money to fund it, IE will not.
All I can say that I hope that the current version of IE lives long and that Microsoft keeps iproving it at the current pace. That will ensure that Mozilla will gain marketshare as it races past IE.
Long Live (the current version of) IE
Mozilla has a built-in email program - if that's important to you, then that's one reason to use Moz instead of FireFox. Me? I toggle between using Safari and FireFox. FireFox was indeed faster than Safari 1.0, but with Safari 1.2, I'd say both browsers feel about the same, speedwise. Anyone have benchmarks?
Bob
The PC Weenies: 11 Years of Online Tech 'Too
I tried Thunderbird for a few days last week... it was so riddled with bugs I found it unusable.
In particular:
- massive problems moving/deleting nested mail folders
- massive problems importing from another mail client (Eudora)
- seems to crash sometimes for no apparent reason
- crazy things happened with the preview pane all the time, like it would disappear at random or make itself really, really tiny and refuse to return to its former, big size
- some options tied exclusively to a particular account - e.g. filters - making the mail-checking process less transparent if you have multiple/many e-mail accounts
- seems to be trying to look a lot like Outlook, which is a shame and unnecessary
I wasn't looking for problems - I WANT to use it, and it has a lot of potential, but right now I'm not gonna use it myself and I couldn't in good conscience recommend it to any non-technical people.
Read Pynchon.
Does anybody know why they stopped putting Talkback into the OS X pre-release versions since 1.6 alpha? I thought that was supposed to help them find crashing bugs. Kind of hard to do when you forget to put it in there in the first place.
#naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
The developers consider quicklaunch functionality to be a hack.
http://extensionroom.mozdev.org/more-info/mngsuppo rt
That's a plugin for MNG support in Mozilla/Firefox. I would read the comments, though, some seem to warn against installing the plugin for certain builds. I only glanced over it, though; MNG support hasn't really been a priority for me, especially since I didn't even know MNG existed until people complained that they took support for it out of Mozilla.
Back when I designed graphics accelerators for a living we did a whole bunch of work trying to figure out what 'faster' ment - at least from a subjective point of view - turns out if you graph actual performance to subjective performance there's sort of an S curve, on the left it's dog slow and people are just annoyed, on the right it's so fast people don't notice performance is an issue at all and in the middle there's a vaguely exponential region where if every time you make things ten times faster they think it got better, maybe by a subjective factor of 2 .... 10% is in the noise .... unless your UI is in that far left dog-slow region
Are these speed / size / page-load figures accurate for the binaries with the debugging code still in?
If so then these performance gains will be even better once the debugging stuff's taken out for production. Will they not?
C-x C-s C-x k
This isn't a troll its funny, oh well, But I wish everybody would just do MNG (and PNG for that matter) right, GIFs are so limiting.
Basically, the Any Browser campaign says to write everything to HTML 4.01 "Strict". Use CSS for all layout. Mozilla development fits this very nicely. Check out Eric Meyer's CSS/EDGE. Everything at CSS/Edge fits with the "AnyBrowser" way of doing things, but yet not everything at CSS/Edge will load with Internet Explorer.
In my own less complex pages, I've found that I can make a page load /similarly/ in both, but I can't use HTML "Strict", unless Internet Explorer starts to choke (throwing everything to the left edge when I wanted it centered, etc.).
So, as the above post mentioned, you end up writing to Internet Explorer, but you loose compatability with some "text readers for the blind", lynx, etc.
Ah, but who cares if a blind person can read your web page. Well, maybe your web page isn't just a collection of photos, maybe you have something of interest. Then, you should care.
Bottom line, the user will think that you're web page is broken if it doesn't load in I.E., and you loose readers this way. So, you end up with a web page that is a little more sparse, and less feature rich than you wanted.
OK, I'm glad there's a new Mozilla release, and I'm glad it's a little faster, but calling the 5% - 9% increases "dramatic" is a little much, don't ya think?
Dig up a bit in the forums. I'm using a Athlon XP optimized build (with all that black magic voodoo compiler switches). If you have the hardware to support it, you can REALLY feel the difference.
It would seem that the definition of "dramatic" just got marginalized. Personally I'd think of a 2x performance increase as dramatic. 1.1x is what I'd term "laudable".
- First they ignore you, then they laugh at you, then ???, then profit.
You will not be able to go to a fair of almost any kind without seeing mozilla used (I've been to quite a few that had little or nothing to do with computers and seen mozilla or a browser using the gecko engine used).
You, my friend, have obviously not been to the Bandera County Rodeo and Fair. Absolutely no Mozillas to be found, though there are some nice heifers!
I assume these speed changes will be transferred over to Firefox as well, since it uses the Mozilla code base. That will likely make Firefox amazingly fast, since it's already faster than the stock Mozilla.
-------
"In times of universal deceit, telling the truth becomes a revolutionary act."
-- George Orwell
As mentioned in this Footnotes article, the new Mozilla supports smb:// browsing through gnome-vfs, and the integration with your GTK2 theme has improved.
Life is offtopic.
Every time I use a different web browser, whether its Mozilla/Seamonkey, Firefox, Opera, or even IE on Windows, I'm sure it feels faster than whatever I was using before. It doesn't matter what it is or how slow it is (unless it is really, really slow, like old Mozilla versions -- but even with them, I had myself convinced that some versons were dramatically improved from the last one, when they really weren't).
This was bothering me the last time I was playing around with Firefox. There is no reason for there to be any difference in rendering performance at all between any Gecko browsers using the same version of the rendering engine. A different user interface will not change that.
I decided to test this for certain. I got Seamonkey, Firefox, Galeon, and Epiphany, all running of of the same Mozilla version (okay, Firefox was actually a somewhat newer trunk snapshot, and had some optimizations, so if anything it should have been faster). I opened them at the same time, and in sequence, went to the same sites and watched them render. I loaded sites repeatedly from cache, and tried other sites I knew weren't cached. There was no difference at all. Every time I thought I noticed a difference, I went back to the other browser and loaded the same thing. It took the same amount of time.
I didn't see a "many percentage point" difference. All of the percentage points of difference were within the margin of error of my ability to distinguish differences in time, and while that could be a problem, all of the things I checked took long enough on my computer that if there were a significant proportional difference between browsers, it would manifest itself as a subjectively perceptible slowdown.
As for rendering, if you see any rendering quality differences between gecko browsers you need to check your font/screen dpi settings, because they ought to be exactly alike.
Firefox might be a nice browser, and it has its merits in terms of UI feel and features, but it won't succeed by being faster than Mozilla/Seamonkey, because it isn't.
"(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
I guess that makes it.....
29% Better!
-L
Don't Panic.
Part of the problem there is that animated GIFs are still considered images, whereas MNG is probably considered video (since its mime type is... video/mng? Or is it video/x-mng?.) Therefore any site which only permits images to be displayed on it (various bulletin board sites are the main culprits, I suspect) might still cripple MNG supporters.
Unless you really can have <img> tags which contain MNGs, in which case I'll STFU.
Karma: It's all a bunch of tree-huggin' hippy crap!
Camino 0.8 is on the way too.
22 January 2004: We are in the process of driving the Camino 0.8 buglist to zarro boogs. We will be branching off Mozilla 1.7 (now scheduled for April) and will release shortly after. We expect Camino 0.8 to be faster and even more solid than 0.7...
Okay - Firefox I understand. Lots of people just need a browser at work, for instance. But to be honest, if I need an email program I probably need a browser. What's the advantage of a standalone email client?
"Sometimes a woman is a kind of religion, she can save your soul & set you free from all your sins" - Bad Examples
From the GoogleBar FAQ:
Someone told me that this works in Netscape and Firebird. Does it?
The answer is both yes and no. The toolbar works best in most recent versions of mozilla, since this has been where development has occurred all along. Due to XUL changes in the mozilla versions following the release of Netscape 6.2, the Googlebar will not work at all in any release of Netscape 6.2.x or below. However, in Netscape 7, which is a close cousin of recent mozilla versions, the Googlebar works. It has also been tested to work in Phoenix/Firebird 0.2 and above.
With a little help from me, I have gotten 10 or so Windows users at work to start using Mozilla, and one of them even tried out Firefox before I did! However, on the down side, I haven't gotten any of them to try Linux, though several have said "they should". I might just burn Knoppix to CD for them and hand it out.
./ , then it can do the rest of the work ( converting )for me. :)
Anyway, IE does have greater "marketshare", but all it took me was a few nudges to get Windows users to switch. Now if I can just get them to change their homepage to
All this from a former MCSE who though Microsoft was the end-all be all and Linux was just a flash in the pan...
I can't afford a sig!
The Mozilla suite and the Firefox, K-meleon, and Camino browsers all use the Gecko engine. The Konqueror and Safari browsers use the KHTML engine. Apparently, the KHTML developers have a more pragmatic policy with respect to implementing MSHTML extensions *cough*document.all*cough* than the more standards-minded Gecko developers.
In only a matter of seconds, I'm not going to notice less than a 10% improvement on an application's speed. With something like Photoshop, maybe that would matter.
Of course, I'll download it anyway, because I always update my browsers upon full (non-beta) releases. Just waiting on the full 1.7 release...
Well I for one welcome our new MNG overlords, but I just don't see anything happening unless people get enough impulse to stop using GIF. And there's also that slight problem of the other, more broken browser which can't implement many other standards well, including PNG, and has even less chance of getting MNG right.
Karma: It's all a bunch of tree-huggin' hippy crap!
Be careful when using setInterval() and setTimeout(). Mozilla 1.3 cannot use setTimeout() recursively to create the effect of setInterval() without maxing CPU usage. setInterval() works fine. If you want something to happen at regular intervals, use setInterval() to make all browsers happy.
---
One issue where the browsers are different is capturing key events:
MSIE6 requires:Mozilla1.3 works with:[addchar() is a generic function to handle the processing of each key regardless of the browser.]
[Why did Slashcode add a space within the ECODE tags?]
Luckily both sets of code can be on the same page with the KeyPress event being set correctly without testing for the browser names. I prefer the second method because it allows the code to be contained in a
To be on-topic:
Does Mozilla1.7 allow for the awful event model of MSIE? Will this code still work?
I spend my life entertaining my brain.
And so the beast became agile. The unbelievers fell silent and the followers of
Mammon were left behind. The beast had been improved and awaited the release of
the great FireFox.
from The Book of Mozilla, 1:7b
(Red Letter Edition)
I followed the link to the article.
I couldn't find anything about what those percents mean.......ie how many seconds faster on what kind of hardware.
Its a step in the right direction though
Wait - what sort of person quits Mozilla after firing it up? I usually have at least five Mozilla windows open. The only time I have no Mozilla window open is immediately after a reboot. I suspect that for most users, Mozilla's absolute paging behavior (what happens when you quit it entirely) is a non-issue except how it handles the creation and destruction of additional windows beyond a certain low number.
The flag just makes more sense than the constitution. - Judas Gutenberg
Mozilla 1.7 size and performance have improved dramatically with this release. When compared to Mozilla 1.6, Mozilla 1.7 Beta is 7% faster at startup, is 8% faster at window open time, has 9% faster pageloading times, and is 5% smaller in binary size.
Dramatically? I don't know about you, but an 8% increase in speed and 5% decrease in size doesn't seem very dramatic to me. Mozilla is okay, but still fels like a truck compared to Opera.
RMN
~~~
Does this have anything to do with Firefox's string changes which reduced the code and increased speed by about 5%?
How could I tell? There are no pages I could test it on...
...and everyone knows it. :) KDE is obsessed with becoming Windows. They even integrated the HTML browser and file browser--there is *absolutely no point* in doing that, and now I have to wait through seconds of lag time to open simple folders.
All the volunteer effort in the world and what do we do? We make another UNIX. Then we make another Windows on top of it!
I disagree. I've yet to find one person who raves about how "stylish" and "good-looking" a web site is an then points to a website that isn't a pain in the ass to use.
Let's take a look at your mezzoblue.com example:
* Uses inconsistent highlighting -- background rollovers (ugh) on part of the text like the "also available" websites, underline rollovers on other parts like the "Designing with Web Standards" link.
* It uses images for text in its heading. At the moment, I am sitting back fram my computer and leaning on a recliner. My face is about 1.5 to 2 times my normal viewing distance, and I use 1152x864 on a 17" monitor, which is already a high resolution. Normally, I just bump up the text size and have no problem reading a website (as do disabled people). This website's topic entries are unreadable to me, and I had to lean forward plop my face right next to the screen to read the "also available" heading. Heck, that's damned small text even for a lot of glasses-wearing older folks that I know of, with no way to work around it.
* The site uses rollover menus. I don't think I know *anyone* that likes using rollover menus -- I *really* hate it. It doesn't even use your typical old annoying rollover menu -- this has an image background or something. It took ten seconds or so for the image to load, so I had floating white text on a light blue background for a bit. It was pretty unusable.
* Widget functionality is unclear to a viewer. Once again, the analysis I've heard of rollovers holds true -- they're used by designers that have such an unintuitive design that they require the user to wave the mouse around over the interface to figure out how it works. There are rollover menus in the upper top corner. There's no visual indication that these little dinky images are, in fact, rollover menus. It wasn't until I started scanning the page with my mouse cursor that I figured it out.
* Confusingly chosen and similar visual indicators. The mezzoblue.com site uses a diagonally-upward-aiming triangle to indicate a menu (*most* of the time). For starters, this indicator is inconsistent with the common desktop use of a downward-aiming triangle to indicate a popup menu. It is also almost identical to the diagonally-downward-aiming triangle that is used to indicate a section header *on the same site*. Not only that, diagonal triangles most common use in current HCI is for a half-open expandable section of data, a convention from Mac OS. The sections look like they *might* roll up when clicked, but do not in fact do so.
* Dissimilar widgets are visually identical. If this designer *had* to make rollover menus and grokked HCI (a dubious pair of bedfellows to begin with), he'd know that one does not make widgets that operate differently but appear identical to the user. Up at the top, we have three blocks of text that appear the same (upward-diagonal triangle, text). The first two ("about", "weblog") are rollover menus. The third, "contact", is a link. When I started rolling my cursor over them, I sat and waited on this link, assuming that my browser was just slow to pop up the associated menu.
* Text colors poorly chosen for readability. Much of the text/background combinations involve two very similar shades of blue. Most of this is readable to me at my current viewing distance if I increase the size, but I know many people that would *not* be able to comfortably read such text.
Honestly, mezzoblue.com seems an excellent example of why sites should *not* be "stylish" -- when designers use "stylish" as an excuse, they're frequently making websites that are simply poorly built from an interface point of view.
Finally, as I've argued before, a lot of people making "stylish" websites with "extra zazz" are people that are familiar with the conventional way products are sold. Most products need to appear flashy, interesting, and novel just long enough for a person to impulsively choose to buy them. For conventional products, "flash" h
May we never see th
If you double-click on each download in the Download Manager, you'll get access to pause/resume features. That feature has been there for while. Of course, in the Firefox Download Manager these features are shown up front.
zWhat would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
The Google Zeitgeist shows their current visitor breakdown as a graph. It isn't labeled, but by breaking it down and determining which pixel the lines fall on at the end, the percentages look like this:
Internet Explorer (5/5.5/6): 89%
Mozilla/Netscape (5/6/7): 5%
Unknown/Other: 6%
Portable versions of Firefox, GIMP, LibreOffice, etc
You all might snicker at the single-digit speed improvements in the latest release, but I just upgraded from 1.2 to 1.7 and the difference is not only noticable, it's unbelievable! Especially the startup time, must be a quarter of what it previously was (no preloading in memory under linux, startup times for mozilla used to be awful)
The GUI is also much snappier.
I see good days ahead for Mozilla. A few days ago, a non-techie friend of mine saw me using Firefox and inquired about it. Once he installed it and saw the tabbing, pop-up blocking, speed, and skinnability, he immediately set it as his default browser. Though IE is the most common right now, people will find about the quality of Mozilla sooner or later. Actually, who cares? Even if they don't, I and all my friends still get to use a superb browser
TerraIM - my pet AIM client project.
That sounds very interesting, gotta try it out (PowerBook + G5 DP). Although I have another issue with Mozilla on Linux though.
:-)
When accessing shockwave/flash pages, Mozilla (and Netscape, and Opera) crashes on me rather frequently. It happens atleast a couple of time every business day. I just copied the plugins from the standard Netscape 7.1 distribution.
Are there any other shockwave/flash plugins that I can use that dont bring my browser down all the time ? Any hints/tricks/tips greatly appreciated! (Apart from trying out Mozilla 1.7
Probable impossibilities are to be preferred to improbable possibilities.
Aristotele
I dont know quite what went wrong, but Mozilla's development just spiralled upwards into features and bloat year ago. That is bad considering its the only really free standalone browser. If youre running say NetBSD on some exotic hardware, or Solaris on x86, or something not mainstream, youre really stuck with Mozilla unless you can get around the overhead of KDE/GNOME and use their browsers.
Mozilla firebird/thunderbird has caught most peoples attention and can be far more popular than mozilla if it didnt crash so much. For now, people with exotic setups will have to use lynx, keep trying mozilla and firebird intermittently and turn back to Windows or Linux on x86 when they get frustrated. I do wonder whose interests is Mozilla serving anyway with such extreme bloat.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Firefox roadmap. Plus, it's been announced on mozillazine.org in even greater detail.
CSS2 and Mozilla (not I.E.) can do full roll-over menus without the help of scripting. But this does NOTHING on I.E. Similarly, microsoft.com has menus (in black, top right of screen) that do nothing unless I.E. is loading them).
If your boss/client wants menus like that, then there is no choice but to break the Any Browser campaign (which I believe in), and use JavaScript (or Server Side Includes) to create different pages for different browsers - again, breaking many browsers that spoof their headers, or otherwise lie (Opera, "MSIE Compatible").
Firefox *is* faster than Mozilla 1.6 (and Galeon using Mozilla 1.6). Try loading a large page like http://www.gnu.org/software/libc/manual/html_mono/ libc.html
When loading in Mozilla, my CPU usage was at 100% for 22 seconds. When loading in Firefox, 100% CPU usage lasted for 16 seconds.