[pecg]

This is a definitely an interesting approach. What is the web engine behind it? I thought about the idea on building a simplified interface for blink and V8, but they are extremely and differently glued to other pieces of software in each Chromium release, that it is indeed hard to keep track on them.

[digi_owl]

Looks like whatever webkit variant they can find.

https://github.com/nEXT-Browser/nEXT/tree/master/next

"Use CCL Cocoa Library to use native webkit backend"

[pecg]

My bad, I missed that comment, was even reading the source code trying to find something about it. Thank you.

[digi_owl]

I find that if i want to find out what something is made of, start with the dependencies in the build instructions.

It may not always help, but it seems to work often enough.

This time however it was in the version history, go fig.

[The-Compiler]

You might want to look into QtWebEngine or Chromium Embedded Framework, which give you a stable API over Chromium's content API.

Then again, this sounds a lot like qutebrowser ;-)

[zeveb]

I believe that it's using Qt's WebKit API. I don't believe that it has ad blocking yet, but that's a Simple Matter of Programming™.