Linked by Thom Holwerda on Wed 9th Jun 2010 20:12 UTC
Amiga & AROS After much, much development, the developers behind AmigaOS 4 have released the first alpha of Timberwolf, the AmigaOS 4 port of the Firefox web browser. I tried it out on my Amiga, and indeed confirmed that this is very much alpha material.
Thread beginning with comment 429390
To view parent comment, click here.
To read all comments associated with this story, please click here.
Neolander
Member since:
2010-03-08

....you already have a WebKit browser. Dump the money into bringing it up to speed wit Safari and Chrome. I don't get it. I wouldn't touch Mozilla for the last 18 months on my Mac because WebKit has gotten so much better, why would anyone want this? On a platform that needs a solid web browser, why would they make the same mistake the Be people made?

How is webkit "so much better" ? It's a little faster, yes, but Firefox 3.6 is reasonably fast even on older hardware (contrary to, say, IE7). It sounds way easier to port. But as a user, does Webkit really have some serious benefit over Gecko ?

Edited 2010-06-10 07:56 UTC

Reply Parent Score: 2

renox Member since:
2005-07-06

But as a user, does Webkit really have some serious benefit over Gecko ?


If it's used in a multiprocess setup like Chrome do, yes as this allow the user to find easily which tab use too much memory|CPU and close it (and this can be used also to improve security), otherwise no..

Firefox devs are working on a multiprocess version of FF, but I don't expect it anytime soon: this kind of big change must be quite difficult to do..

Reply Parent Score: 2

Neolander Member since:
2010-03-08

I agree with the multiprocess thing, myself because I hate seeing a plugin crash leading to loss of data, but as you said it's not part of Webkit itself (making it so is the goal of the Webkit2 project), it's only part of Chrome/Chromium's implementation.

Firefox as a Gecko frontend could just do the same thing and open one new Gecko process per tab without in-depth work on the underlying engine. It'd be a performance nightmare, however, because Gecko has not been optimized for such use at all, hence we'd get 100 MB/tab memory usage and such.

Maybe there would be some incompatibilities with legacy code as well, but usually rendering threads of several tabs should not interfere with each other.

Edited 2010-06-10 09:37 UTC

Reply Parent Score: 2