Re: [dev] [surf] Switching to webkit2 as default

From: FRIGN <>
Date: Thu, 4 Feb 2016 19:16:09 +0100

On Thu, 4 Feb 2016 17:50:05 +0000
Nick <> wrote:

Hey Nick,

> I try not to keep too abreast of things like GTK and WebKit, for the
> sake of my sanity, but I read this[0] today which was a pretty scary
> read, really.

I also read this article a while ago.

> One thing that is particularly important is that webkitgtk2 is
> receiving security updates, whereas webkitgtk1 is not, and hasn't
> for quite a while. I was not aware of this. Web browsing is a
> dangerous thing, and I didn't realise quite how many known
> vulnerabilities I have been surfing with, and would like to reduce
> that number.

Thing is, to use the only sane backend we would have to port surf
to GTK3. I am not that deeply involved in surf development, but given
there are other backends around (the Chrome blink backend for example
and others) it's not an easy decision to make.
In my humble opinion, I like the Chrome backend because they cut out
considerable amounts of Apple legacy stuff, whereas the normal webkit
a bit more crufted (all webkit versions are bloated).

> I know there's a webkitgtk2 branch of surf. Is there anything
> missing in it that would prevent it from being the default surf
> branch? I'll gladly help bring things up to scratch if there is work
> to do, as surf is a reasonable interface and I dislike it much less
> than other browsers (except my pandoc / markdown / tkread setup, but
> that's not very general-purpose, only really fit to read longform
> articles).

It would make sense to look into this. It always makes sense to be
on the latest branch to get the latest security updates. Let's see
what the others have to say.



Received on Thu Feb 04 2016 - 19:16:09 CET

This archive was generated by hypermail 2.3.0 : Thu Feb 04 2016 - 19:24:10 CET