K-Meleon and Firefox

MozillaZine is running a story about K-Meleon 0.9 being released. It didn’t take people very long to compare it to Mozilla Firefox 1.0.
That said, I’d really like some in-depth reviews of each product against the other. Maybe one of them has features that the other could implement.
Please, no “they suck, use this” comments. 🙂 I’m actually not biased either way. I’ve had good and bad experiences from both Firefox and K-Meleon in the past.
UPDATE: I just spotted an article on PCMag about what essentially adds up to overclocking Mozilla Firefox. Note I don’t necessarily approve of this idea (I don’t care for overclocking anything I have), but I hadn’t seen it on planet yet. So I wanted to get some feedback from the mozilla.org community on it.
Use at your own risk! If you file a bug at Bugzilla that can’t be reproduced from a normally-configured Firefox, but is reproducible from an overclocked one, don’t be surprised if someone (not me) marks it INVALID.
I have no idea if it works on K-Meleon, and I’m not that enthusiastic to find out.

6 thoughts on “K-Meleon and Firefox”

  1. Just for anyone else who might read this, pipelining does indeed work on K-Meleon (and Galeon/Epiphany, and just about any other Mozilla-based browser).
    It’s usually harmless on the client end, but it’s very rude to small webservers. (since it opens up a large number of simultaneous connections)

  2. This is old hat, you can find it on http://www.mozilla.org/support/firefox/tips.
    – network.http.pipelining
    – network.http.proxy.pipelining
    Seamonkey even has a UI to alter these preferences. They are switched off by default because there were some buggy web server implementations that didn’t handle pipelining properly.
    – network.http.pipelining.maxrequests
    I’m not sure, which value is ok here, but mozilla.org themselves are suggesting 100.
    – nglayout.initialpaint.delay
    This is the delay before starting to layout. If you set this to 0, Mozilla is starting immediately, but several redraws might be necessary.
    So, all of this is not very dangerous.

  3. i used k-meleon before switching to phoenix 0.3 (back then it didnt have tabs/layers), it was ok but phoenix was way better.
    tried the new version and i like it very much, uses half the memory firefox 1.0 uses (even with 40+ tabs open) but it’s skinning system sucks. IMO the way tabs were implemented in k-meleon is better. They basically are new windows contained in the first one, not in a mdi, it looks basically like firefox’s interface, but any of the open pages (or alltogather) can be detatched from the main window. Also groups of tabs are cool, you just tipe the name of the group of favourites and press ctrl+enter (or was it other key combination, dont remeber) and they open.
    Needs more configuration options, and better skinning, but im defenitely keeping it (actually im going to keep an unnoficial version which is based on mozilla 1.8, cant stand using a 9 months old engine).

  4. “It’s usually harmless on the client end, but it’s very rude to small webservers. (since it opens up a large number of simultaneous connections)”
    No, that’s what happens when you increase max-connections. Pipelining doesn’t open up any more connections (in fact, if you have more connections, it generally means that pipelining doesn’t get used, because pipelining will only happen when there are more requests than the maximum number of connections)
    “- network.http.pipelining.maxrequests
    I’m not sure, which value is ok here, but mozilla.org themselves are suggesting 100.”
    Which is totally stupid, as the values that actually work are from 1 to 8. You can set it to 8, 10, 100, or 54698 and the program will use a value of 8.
    The tips on the support pages come from contributors – they’re not necessarily any better than what you might read in a blog or forum.

  5. The maximum number of open requests (network.http.pipelining.maxrequests) is 8. You can set it to 1000000 if you want; the result will be the same as if you set it to 8.
    As for nglayout.initialpaint.delay, be aware that setting it to 0 can result in both a “jumpier” layout process and a longer total rendering time, although it should allow you to see useful content sooner.
    The definitive guide to these and many, many other tweaks is http://forums.mozillazine.org/viewtopic.php?t=53650

Comments are closed.