If you’re all too familiar with the foxy browser (turned DCS mascot), you should also be aware that it’s all too prone to memory leaks. It’s the primary suspect when people complain about its hang-ups and slowdowns after extended periods of usage. I’m an unhappy
But a certain Firefox add-on called the Leak Monitor might just solve the problem. Just a few moments ago while using a very AJAX-y page a dialog popped up to inform me that were was, indeed, a memory leak caused by the infamous prototype.js. I’m not too fond of the said script as it is too large for its own good and wish more people would use moo.fx and its relatives like mootools, which have a tinier version of prototype.
Of course that’s not the only possible reason I’ve been experiencing those hungapp crashes; it may very well be the sheer number of add-ons I already have, or it might be just one of them. Either way, I’ve decided to reacquaint myself with Flock for miscellany I’m browsing. Web Developer Toolbar and FireBug (and IE Tab!) are indispensable for HTML/CSS debugging, but when I just need to watch Nodame Cantabile or Honey and Clover on YouTube*, that self-proclaimed Web 2.0 browser isn’t so bad. The built-in feed reader is also very appealing. However, I think Flock needs more time to be a little more like Firefox in terms of its user interface and community support. It also needs to incorporate way more “social” features, e.g. Meebo, StyleHive, out of the box.
Poor Opera. There’s just something about its UI that I can’t get used to, but that doesn’t mean I’ve given up on it. Will try juggling the three from now on.
I think there are some anime matters I need to get off my chest, among other things. Maybe in the next post.