Chimera Not Dead Either
Tuesday January 21st, 2003
Yesterday, Chimera lead Mike Pinkerton posted a weblog entry in which he said that he was considering ceasing Chimera development. This lead to a Mac media frenzy, with stories at MacSlash and Slashdot. In a new blog post today, Pink has clarified the situation: Chimera is still alive. Mike, who would like to point out that he is not the only developer, was just having a bad day and the project will continue on its quest to make a browser that sucks less.
#9 Re: Not enough reaction
Wednesday January 22nd, 2003 6:58 AM
You are replying to this message
(For some reason we're talking about windows browsers in this thread, but hey)
You know, fact is, in terms of interface (which, you know, is what I actually spend my time using) Mozilla is my favourite browser.
In terms of speed it loads fast enough and it loads Web pages fast enough. there's no significant difference with other browsers. (there might be if i loaded my web browser 20 times a day. i don't).
Phoenix is ok too (configurable toolbars = good idea, sure), but needs improvement - well that's why it is 0.something right now.
K-meleon is a horrific piece of crap. If I wanted to use it I'd just use IE only somehow with a new 'make the interface worse' plugin. (Ok, page rendering is better, but that's it.)
People have to get off this 'bloat' kick. I don't use mozilla email. i don't use mozilla news. I certainly don't use chatzilla, which is godawful. How much does it matter that these unnecessary (for me) programs are included in my web browser? NOT ONE BIT. Not at all. I don't care. Ever.
Fact is the web browser uses what - maybe 25 MB (of actual memory, plus maybe another 25 in VM) when you've got a bunch of windows open? Who cares? Out of a reasonable minimum, say 128 MB, that's not a huge proportion. (If you have less than 128 MB then trust me, you're in a tiny minority, and you're a problem that's going to go away as you upgrade.)
Though obviously it's important not to let these things get totally out of control, and download size remains an issue while people still have modems ((So for example a phoenix-style architecture based on plugins so that people who want the web development tools, like me, can have them but others can save a few hundred kb download by not having them, is a good idea)), in general if you are thinking about putting a lot of effort into making code smaller it's *much* better to spend time dealing with problems that will remain or get worse in future - e.g. usability problems - than with problems that are already small and will vanish in future - e.g. memory usage.