Slashdot Mirror
Moving towards Mozilla 1.0
fluedke writes "The latest Mozilla CVS identifies itself as "Mozilla 1.0". It looks like this source will become the official 1.0 within the next days. Read the news posting here." And if you're one of the missing hackers, speak up.
I doubt MS will develop anything for Linux. Why would they? The kind of people who use Linux are typically people who hate them and are trying to get away from them. And of course making applications for Linux will only help reduce Windows market share.
With the crappiness of IE6, especially with its bug that causes favorites to open in the first browser window instead of the window that requested it, this should be no concern.
All it needs is publicity, it already blows IE6 out of the water.
. Reporting bugs is almost an art, and if approached with a humble and helpful attitude can be very helpful.
Humble? By submitting bugs we're helping them, not the other way around. If they ever want to have a useable product, they need to fix their big bugs, period. Fuck being humble. Either the developers fix the bugs or not.
I'm not a coder, but I'm an *experienced* beta tester and I've worked on longterm volunteer projects that involved a pack of professional programmers with a dedicated testing team. IOW I'm not a beginner at this. I *do* know how to recognise and document bugs (in tedious detail :) Frex, on one project, 75% of bugs and performance issues listed in the changelog were those I'd found (and there were 8 core testers in that group).
But turn it around -- the problem I see, with Mozilla and too often elsewhere, is that testers get no respect, no matter how good they are at that job (IMO, itself as necessary as coding! What use is beautiful code that doesn't work right?) Coders too often consider testers a nuisance at best and a hazard at worst ("how dare those scum break my perfect code!")
Coders need to respect testers' work as well, but all too often the tester is treated as a second-class worker who has no right to a viewpoint on how the program should behave, at least if the coder doesn't feel like fixing the issue at hand. How does a coder expect to get and keep respect from testers if they don't feel they need to respect their testers in return? I realise bugs need to be prioritized and all that, but there's a difference between marking one "low priority" and entirely blowing it off as being too much of a PITA, or "not what *I* want" even when users are clamouring for it. (Ooops, I forgot, Mozilla is for *developers*, not for lowly users!)
And *that* is the problem I've observed with Mozilla. There are open issues that have hundreds of "votes" to fix, which remain unfixed because the coder doesn't LIKE that feature. (Check out some of the context-menu issues for examples.) Not part of the coding group? Then your opinions, and your bug reports, don't count.
~REZ~ #43301. Who'd fake being me anyway?