Mozilla Branches for 0.9.8
Wednesday January 23rd, 2002
mozilla.org today branched for Mozilla Milestone 0.9.8, as well as opened the tree for 0.9.9 checkins. Look for branch builds to start sometime later this week, as early as tomorrow. (While a certain site believes that without builds, you can't have a branch, that is not true.) Pre-0.9.9 trunk builds will start tomorrow, or possibly tonight. See our earlier story for what's new in 0.9.8.
#28 Re: Re: Re: Problems
Friday January 25th, 2002 9:02 AM
You are replying to this message
I know it's a volunteer effort and all that, but I still think that's a pretty sucky attitude. Everything that Strauss was pointing out was true. The site used to work nicely, except for a few (very rare) database connection problems. Lately, it has taken a turn for the worse. I know this was done in the name of making the site lighter, but the method of making it lighter is a little weird, since it means the site is broken on a lot of browsers. You probably remember that I was complaining about it earlier (maybe a week or two ago) and it has considerably improved since then, at least on IE 6. But for example the talkback editor textarea (where I'm writing right now) is *WAY* too wide, which makes it impossible to see about half of the textarea. Things like this would be really easy to fix, but would make the whole site a lot more usable for those that aren't using Mozilla as the #1 browser.
Strauss is a very good contributor with lots of good advice, ideas and opinions. While his views are not so commonly shared here, he presents his opinion and arguments very clearly. He is a much needed "second opinion". Losing him because the site has been broken on his web browser / platform would be pretty sad. Going "feel free to not return", I must say, is beyond sad. It's actually very lame coming from the admin of the site!
As far as the HTML and database problems go, I don't see why it's such a big problem. If there's only a limited number of database connections available, just do a wrapper around whatever code is now returning database connections, and have it wait if there's no connection available (a certain connection count is exceeded). A simple mechanism like that would not even slow down the site, except for the few situations where there are no more free connections.
I also have a hard time understanding how it's so hard to make cross platform and light HTML, because the site isn't really that complex in it's layout. If it was a will to do it "right" (using only CSS and no tables etc. for layout) then I could understand it. But the primary motivation was to make it lighter. It wouldn't be hard at all to change the HTML slightly and achieve both working layout on all browsers as well as lightweight HTML.