Galeon 1.2.x, bugs and work-arounds

Galeon 1.2.x, bugs and work-arounds

Posted Feb 26, 2004 23:01 UTC (Thu) by nial-in-a-box (guest, #19824)
In reply to: Galeon 1.2.x, bugs and work-arounds by jvotaw
Parent article: A grumpy user's browser review

I don't understand how the author of this piece can even seriously consider using a piece of
software with such a blatant memory leak. While this could be the fault of his/her particular
configuration, it does not seem that any effort was made to research this. Sure, one bad thing
should not totally remove this browser from consideration, but it should not still be considered a
preference with such an obvious flaw. Even if this doesn't exist for other users, I fail to see how
the editor can still like this browser. This is equivalent to an auto review where the reviewer
gives a favorable rating to a new car that overheats if you don't shut it off and start it again every
30 minutes, simply because he/she happens to enjoy the way the seat feels. Unless you don't
give a shit about having to close all browser windows when you leave your workstation for a
while, or you have several gigabytes of memory, this is not acceptable. I assume that the
problem has been fixed by now, but please don't continue to give favorable reviews of flawed
software. Developers need good, accurate criticism if they are to make good software. If they
are praised for flaws, we will just have Microsoft products that developers aren't getting paid for.

---

(Log in to post comments)