4 ms·
There are also surf https://surf.suckless.org/ https://surf.suckless.org/ and qutebrowser https://qutebrowser.org/ https://qutebrowser.org/, both based on webki
by dependenttypes 6y ago
There are also surf https://surf.suckless.org/ https://surf.suckless.org/ and qutebrowser https://qutebrowser.org/ https://qutebrowser.org/, both based on webkit.
- imiric 6y agoI use my own fork of surf daily, but am having to fallback to mainstream browsers quite often these days as sites stop working on it or it's unusably slow. Slack no longer works, GitHub breaks occasionally, etc. Is there a well-maintained fork that fixes these issues? The main repo[1] hasn't seen updates in over a year now. I read that development slowed down after the main maintainer left suckless, but I'm hoping the community will pick it up. It's an excellent minimal browser. [1]: https://git.suckless.org/surf/ https://git.suckless.org/surf/
- The-Compiler 6y agoFWIW Slack seems to work fine in surf for me. Are you sure you have an up-to-date WebKitGTK on your system? Those kinds of issues are typically fixed there, and not in surf itself. As long as the WebKit API stays backwards-compatible, there's probably not much need for surf to change (other than for new features). There's zsurf based on QtWebEngine/Chromium too, FWIW: https://github.com/SteveDeFacto/zsurf https://github.com/SteveDeFacto/zsurf
- dependenttypes 6y agoThere is also badwolf https://hacktivis.me/projects/badwolf https://hacktivis.me/projects/badwolf (again based on webkit)
- The-Compiler 6y agoqutebrowser uses QtWebEngine by default, which is based on Chromium. You can use it with QtWebKit instead, but given that's based on a 2016 WebKit with no process isolation or sandboxing, I wouldn't recommend it.