Before we go digging Mozilla's grave...
by
Frank+Hecker
·
· Score: 5
It might be a good idea to review things as they stand today, as well as a little bit of history. Some points to remember:
First, the Mozilla effort goes on: AOL is still funding development, non-AOL developers are active as well, the project is continuing to release "milestone" releases which you can try out, and this will culminate later this year in beta releases of Communicator 5.0 and then a final release, all based on the open Mozilla source code. This has been the case all along, and remains the case.
Next, in the Mozilla project there was a fundamental trade-off: build and release a product based on the existing in-progress 5.0 code base ("Mozilla Classic") or rearchitect the product to make it more standards compliant (i.e., use the new layout code being developed), more extensible, more open (e.g., use something other than Motif), and so on. In particular, many people complained vociferously that Mozilla/5.0 needed to have 100% standards compliance for HTML 4.0, CSS1, etc. Thus the decision was made (way back in October 1998) to rearchitect the product, use the new layout engine, use GTK+ instead of Motif, etc.
Most people on/. and elsewhere seemed to agree with that decision at the time, and would presumably still agree with it. However from Jamie's point of view it presumably would have been a better plan to go ahead and ship as early as possible even given the downsides. (Also, Jamie saw no reason to ditch Motif for GTK.) That's something about which reasonable people can disagree, but I don't buy the assertion that by taking the extra time to make a better product the Mozilla project has therefore "failed".
Slashdot Mirror
First, the Mozilla effort goes on: AOL is still funding development, non-AOL developers are active as well, the project is continuing to release "milestone" releases which you can try out, and this will culminate later this year in beta releases of Communicator 5.0 and then a final release, all based on the open Mozilla source code. This has been the case all along, and remains the case.
Next, in the Mozilla project there was a fundamental trade-off: build and release a product based on the existing in-progress 5.0 code base ("Mozilla Classic") or rearchitect the product to make it more standards compliant (i.e., use the new layout code being developed), more extensible, more open (e.g., use something other than Motif), and so on. In particular, many people complained vociferously that Mozilla/5.0 needed to have 100% standards compliance for HTML 4.0, CSS1, etc. Thus the decision was made (way back in October 1998) to rearchitect the product, use the new layout engine, use GTK+ instead of Motif, etc.
Most people on /. and elsewhere seemed to agree with that decision at the time, and would presumably still agree with it. However from Jamie's point of view it presumably would have been a better plan to go ahead and ship as early as possible even given the downsides. (Also, Jamie saw no reason to ditch Motif for GTK.) That's something about which reasonable people can disagree, but I don't buy the assertion that by taking the extra time to make a better product the Mozilla project has therefore "failed".