Slashdot Mirror


Mozilla.org Launches Mozilla 1.3

theBrownfury writes "Mozilla 1.3 is out and about. New to this version are features like image auto sizing, bayesian junk-mail filtering, dynamic profile switching, about:config for a pretty view into all of Mozilla's "secret" settings, an initial version of Midas for rich text editing, and a lot of other fixes for performance, standards compliance and site compatability. Also with 1.3 Mozilla is now applying machine learning to improve the autocomplete feature. Mozilla 1.3 is now the official stable release from mozilla.org. Users of all previous versions should upgrade to 1.3 for the latest in features and stability. More info at the 1.3 release page and discussions at mozillaZine.org."

4 of 697 comments (clear)

  1. Re:What about phoenix? by asa · · Score: 5, Insightful

    "Phoenix authors have quit working on it"

    That's not at all accurate. Phoenix developers have checked in changes to thousands of lines of code in hundreds of Phoenix files just this month and Phoenix also picks up almost all of the backend Mozilla changes that happen every day. Just because it's not moving at the pace it did when it was all brand new doesn't mean it's not moving.

    --Asa

  2. not to mention... by Ender+Ryan · · Score: 4, Insightful
    And not to mention... Mozilla is only as bloated as you want it. Either use the installer and don't install anything but the browser, or use the source and do the same.

    Aren't we supposed to be nerds here? Doesn't that mean we should all be capable of installing a fucking browser properly?

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  3. Re:What about bloat by Lord+Prox · · Score: 5, Insightful

    Am I the only one here that is happy Mozilla 1.3 is out? After reading the posts here it sounds like /. would bitch if they were hung with a new rope.

    What is wrong with Mozilla? "Bloat" what exactly is "bloat" memory footprint? HDD footprint? Load Time? Compaired to IE I find it to be very compeditive, plus you are not helping lord gates and mount redmond take over the net/world. You are providing them with a serious challenge which is better for everyone.

    Sorry, I just work up and I'm a little cranky. I don't meean to bitch at the parent post specificly just people that are complaining about nit picky stuff while overlooking all the time/energy spent giving them a free speech/beer answer to IE and redmond (something /.ers also complain about)

  4. They dropped the ball by alexhmit01 · · Score: 4, Insightful

    We looked into XUL as a solution to our content management system about 12 or 18 months ago, I don't remember, and my concept of time is seriously warped from the dor-com days.

    At the time, they CLAIMED that you could do all this cool stuff with XUL, but the documentation (including the 1 ONE official book on XUL, sucked). They all focused on building the GUI inside of the Mozilla browser.

    We were working with a potential partner that has a browser based application, whose bain of existance is IE's print feature (they log printing with their print button, but an IE print would trash that). The idea of a "stripped down" browser that would start at their screen would rock. Additionally, using XUL widgets would let them eliminate the frames and other garbage, making their app easier. They liked the idea of using a XUL toolbar instead of a frame with buttons.

    Unfortunately, weeks of research through their docs went nowhere, and we worked on a Java solution, and the deal went south over time. Now we have our own Java based solution, and don't want to migrate to XUL.

    The XUL + ECMAScript stuff should have been pushed earlier with proper documentation. Instead they pushed it to grab some marketshare when they weren't ready.

    I love Camino/Chimera, and the other Gecko browsers (use Phoenix when on a Windows machine), but they missed a lot of time with not getting XUL as an early solution. They should have put out (early) some shells that you could start from then add your other functionality.

    Sure, other projects have picked it up since then, but with the XUL + ECMAScript solution being the red-headed stepchild for a while, they lost some steam.

    It'll happen, but every year that they wasted will take 2 years to recover, as growth has slowed down and projects chose other tech.

    That said, I love Mozilla now, but I think that the shifting of priorities cost them mindshare that will be painful to recover.

    Alex