AOL Moving to Gecko
Monday March 11th, 2002
Newsforge, and others are reporting that the AOL client will use Gecko, starting with the next major release, 8.0. Along with that, the story talked about AOL's departure from any server platform that isn't linux, and AOL's plans to release a standalone linux client (there aren't any).
This has long been the rumor, and many felt until AOL started using Gecko, it would be hard to get sites to stop using proprietary IE code. This may be the kick in the pants that's needed to help get major sites to allow non-Microsoft browsers access to all of their content.
#36 Work time estimates
by SubtleRebel <firstname.lastname@example.org>
Tuesday March 12th, 2002 2:37 AM
You are replying to this message
"One Mozilla coder could spend one to two days adding document.layers support. Or, thousands of web sites, many of which have been stable for years, could re-open their code base, search for resources to change their code, and then implement, test and deploy those changes. The former option is about twenty person-hours at most; the latter is measured in person-years."
I am curious as to how you have determined that one programmer could implement document.layers support in 20 hours or less. Have you actually sat down and outlined what would be required to complete the task or are you just randomly choosing a number that sounds good to you? I suspect that your estimation was simply fabricated rather than calculated.
BTW, how is it that "one to two days" is the same as "about twenty person-hours at most" when a typical work day is 8 hours? Are you suggesting that a programmer could spend 20 hours in a single 24 hour day and end up with bug free document.layers support for Mozilla? That would be very impressive; I would never have guessed that you had so much faith in the abilities of Mozilla developers.
I also wonder if your 20 hour or less time estimate includes the time required for the patch code to be reviewed, tested, and approved.
Personally I would not mind seeing document.layers support become a part of Mozilla's quirks mode because I agree that it would resolve many of the evangelism bugs without causing any significant harm to the pro-standards position. There are very few new sites being developed that utilize document.layers and I doubt that adding document.layers support to Mozilla would change that trend. However, I would never presume to trivialize the amount of work required to implement document.layers support. If it would really only take you one or two days to code it, then why don't you do it and submit a patch? Mozilla.org may not choose to incorporate it into their builds, but if there was a patch then anyone who wanted to do their own build could include it.