Slashdot Mirror

← Back to Stories (view on slashdot.org)

Mozilla.org Posts New Roadmap

Posted by Hemos on from the updating-the-.plan dept.

berteag00 writes "The mozilla.org staff has posted an updated roadmap detailing the Mozilla code base's relationship to the upcoming launch of Netscape 6."

2 of 170 comments (clear)

  1. Re:That last ten percent... by Hard_Code · · Score: 5

    You know what's even more satisfying that both? Creating elegant and bugless code in the first place. Sure it may sound facetious, but I really do get a lot more satisfaction upon committing rock solid code that does its job right, and is designed well, than coding up some whizbang piece of code in a frenzy then leaving it for poor bug hunters to waste thier lives trawling through for bugs. I'm of the opinion that even if it takes you twice as the first time to get something right, that still far outweighs the penalty of having to come back over and over again to fix bugs. The only "bugs" there should be are either typos, brain-blackouts, or really subtle design issues like threading and locking, etc.

    --

    It's 10 PM. Do you know if you're un-American?
  2. Re:That last ten percent... by rkent · · Score: 5
    /. has seen many articles about all the /stuff/ that gets thrown into Mozilla because it's "k3wl." Is there any information on a Mozilla feature freeze? I don't see any on the site...

    From an outside perspective, it's easy to say this. But, realistically, it's a lot more fun to code in new features than it is to fix bugs. I mean, anyone who develops professionally knows how much cooler it is when your manager says "hey, figure out a way to code in feature X" than when she says "could you take a look at bug A1.006 and check in the fixed code when you're done?" And then you have to sit there and stare at this stupid text box that sometimes pops up and sometimes doesn't for no apparent reason, and check out 4 modules you didn't even think were affected because they're not interacting properly... etc etc etc. Fixing bugs really sucks!

    It kind of goes back to the theory that open source programmers are scratching their own itch when they contribute to a project. And most of the itches have been 90% scratched on this project. So who's still going to be contributing? Fortunately, there's a lot of effort still being put in by netscape; I don't think mozilla has really been depending much on huge fleets of independent developers. And we see how quickly it has gone so far. I wouldn't expect the pace to pick up now that the fun work is over.