Chimera Developer Considers Dropping It

The Infamous Grimace writes "Chimera's developer is seriously considering dropping it, since 'Safari has already won.' This would be unfortunate, indeed. I still use Chimera at times, although it's true that Safari has become my browser of choice." I cannot use Safari regularly, it lacks too many features and has too many bugs. Of course, how long will this remain so? But even if Safari adds tabs and fixes bugs, will they add all the features I need from Chimera/Mozilla, like remembering form passwords, site navigation bar, more fine control of security and privacy? I guess there is always Mozilla if Safari doesn't fit the bill ... but Chimera is so much faster and Mac-like. Update: 01/22 19:54 GMT by P : The web site has been updated: "Chimera's not going [away], regardless of whatever I post on this blog."

Comments

Safari musing

[Matthias Wiesmann]

As for work on Chimera, I understand the feeling of the Chimera team. I agree that Safari is missing many features, it is overall more finished that Chimera. For instance Chimera does not support services well and on my machine it tended to crash a lot.

While some feature will certainly make it to Safari, others will not. It would be nice if Apple would open-source the whole Safari, but I doubt this. Instead, what would be smart from Apple would be to have the browser support plugins, not only for displaying content, but also for controling network operations and maybe some aspect of the GUI. This way people could customise Safari.

As for tabs (the topic of probably 95% of the posts on this post), I don't think is such a good solution. While they are usefull, I feel they are not complete, mostly because the relationship between tabs is unclear: are they at the same level? On the same site?

Most of the time I used tabs, it was to explore some hierarchy and load in parallel multiple branches (say multiple links). What I really would like is something that displays this tree structure, with some options like "pre-load branch" and "attach link as branch". This structure could also use the relationships defined by the link tags. In fact this thing would simply expand the notion of hierarchical history (and in fact include future links). If done well, Safari could use the same panel interface for the hierachy as mail.

Re:Safari musing

[octover]

I admit that I am not your average 'web surfer', I'm a web developer. I love tabs. Why? Because at any given moment I have three to four different pages loaded. Tabs make it very easy for me to switch back and forth without have to go up to a menu to see what is even open. It keeps my screen cleaner which is nice. The other great thing about tabs is that my mom can use Mozilla and never even see them. What is it with the whole tabs are too complex crap? Tabs aren't a default thing on any browser I've come across.

Oh and the relationship between tabs is that they are both 'documents' the browser has/is rendering. That is it. There is no other relationship than that, and I hope that no one gets it in their head to make it more than that (I'm thinking JavaScript and dom stuff).

Re:Safari musing

[Twirlip of the Mists]

My opinion on tabs is well known. I'm not picking a fight here; just offering a counterpoint. I'm well aware that lots of people disagree with me, so don't bother posting just to say that you're one of 'em. Constructive criticism, on the other hand, is welcome.

Because at any given moment I have three to four different pages loaded.

You accidentally point out the biggest flaw of tabs here: they're self-limiting. Depending on window size, you can only fit between four and eight tabs across the window before they have to be truncated. If you can't read the titles, the advantage of tabs evaporates.

With multiple windows, on the other hand, you can have as many pages loaded at once as you want. Multiple windows are not self-limiting.

Tabs make it very easy for me to switch back and forth without have to go up to a menu to see what is even open.

While the usability advantages of a menu over a row of tabs have been discussed thoroughly, it's hard to beat the ease of use of command-` for cycling through an application's open windows. Tabs are useful for up to 4-8 open pages; they are not useful for more than that. Similarly, command-` is useful for about the same number of open windows.

It keeps my screen cleaner which is nice.

On the other hand, it prevents you from looking at two pages side-by-side without jumping through hoops. (Choose the tab, control-click, choose "open page in new window.) Multiple windows can be used in a clean-desktop way (command-M for minimize), but let you arrange your pages however you want.

Oh and the relationship between tabs is that they are both 'documents' the browser has/is rendering. That is it.

That's not really good enough, in my opinion. For example, if tabs were implemented in some way that dealt with #1 problem (truncation), you really ought to be able to drag a tab from one window to another. That's a complicated thing; you have to implement your NSView subclasses as application instances instead of directly associating each NSView subclass with an NSWindow subclass. The current implementation, in which a tab is tied not to an NSView but to an NSWindow forever, kinda sucks. It would make more sense on a large scale for "tabs" (that name is becoming less and less appropriate) to be global network session objects, and for any window to be able to display the output from any "tab." But that poses huge usability problems; how does one instantiate a new "tab?" Should the application manage it for you, creating an autorelease pool of tabs automatically every time you open a new site (by clicking a bookmark or typing a URL or clicking a link that takes you to a new site)? Trying to implement "tabs" right opens more questions than it closes.

But basically my opinion can be summed up in what I've been saying all along: "tabs are a bad solution to a problem that we don't have."

Nooooooo!

[MacAndrew]

Of course, I find something I love and *Apple* of all companies threatens to kill it, indirectly.

I've been using Chimera Navigator for months, forgetting altogether IE (the real villain IMHO). I suppose the sole question for the Chimera team on whether to continue is whether *their* shadowy objectives are being met. The results in the time frame of the effort so far has been impressive -- no, stunning -- much more than a build-a-brower this weekend kind of thing. It really is Mac software.

The single best thing I can say about Chimera -- and there are many nice things, more so now that I've gotten around to poking around with 3rd party mods like SpeedChimera and "PDF Plugin" -- is that I've mostly forgotten about it. That is, it works like the Finder or some other utility that you take for granted and don't give much thought. That's what I've wanted, not the fickle and feature-encrusted IE, just something simple and clean and fast. Safari will learn (has learned?) a few things from Chimera, which tells you something about the latter's value and why it would be a shame to lose the lead-by-example prominence of Chimera.