Re:Mozilla lays off 250 employees while it refocuses on comm...
by takluyver on Tuesday August 11, 2020 @01:32PM
(#24123065)
That's a mug's game. The best you can do is exactly what Webkit does, because that's what you're trying to imitate. You won't do it 100% perfectly (all software has bugs), so in any direct comparison you come out looking worse.
Re:Mozilla lays off 250 employees while it refocuses on comm...
by grey_earthling on Tuesday August 11, 2020 @07:10PM
(#24127033)
The behind-the-scenes API stuff may be no better, but the product's user experience can be better, and that can differentiate it from its competitors.
This is how Vivaldi (and I guess every other Chromium-based browser) pitches itself compared to Chrome.
An aside from the discussion at hand: is it possible to repackage Gecko so that it uses the same API calls that WebKit uses, basically translating from WebKit calls to Gecko calls? The problem with WebKit and Chromium is that all new browsers are going that direction and Gecko is being left behind. This isn't good for the web as a whole. A version of the Gecko API that could be a drop-in replacement for WebKit would be very helpful here, it seems to me.