Hacker News Reader

Comment by telmac | Hacker News Reader

I love qutebrowser but it still relies on a very old Webkit and is not usable on a substantial fraction of sites...

Huh‽ While running with QtWebKit still happens to work, qutebrowser has supported QtWebEngine (based on Chromium) since 2016 or so, and it's been the default since v1.0.0 in 2017. If you're still using it with QtWebKit despite the warning being displayed about it, or using a heavily outdated qutebrowser version, that's on you and not qutebrowser...

If you're running an up-to-date Qt and qutebrowser, that'll currently be based on Chromium 122 from April 2024 (with security patches up to Chromium 131).

Servo when?

I might experiment with it if they improve their embedding story, and if someone (not me) makes it work with Python and Qt.

Sadly, https://github.com/servo/servo/issues/27579 has been pretty dead for the past years.

(And before someone asks for Ladybird backend support: Same story there)

It seems that they moved it since to a bigger meta issue and it's actively being worked on https://github.com/servo/servo/issues/30593. There's wider interest since it is being used in the experimental Verso browser now. There's also ongoing effort from the Qt side: https://www.kdab.com/embedding-servo-in-qt/

Ah, Verso looks nice and active, that wasn't on my radar. I kind of lost hope after a lot of embedding tracking issues and meta-issues over the years (the ones you linked is the third one I've subscribed to I think).

As for the Qt side, "ongoing effort" is quite a stretch for something that was made as a conference demo and not touched again since April: https://github.com/KDABLabs/cxx-qt-servo-webview/commits/mai...

The whole ecosystem is steadily moving ahead. They'll get there eventually I'm sure.

Reply on news.ycombinator.com