I do not think this is a contradiction, at least not from a technical perspective. I am willing to take the responsibility for all actions and modifications I do to my own browser but I need it be secure against all influences out of my control. And I need it come with secure defaults. To be competitive it needs to come without awkward restrictions that e.g. an external sandbox would impose.[1]
I don't think projects like qutebrowser, LuaKit and the many others fit that definition. Not being mainstream means by definition not getting as much security scrutiny as the dominant browsers.
What we really need is a hackable mainstream browser for people that need protection from the bad guys but not from themselves.
[1] I personally would make the concession that supporting a reasonable subset of the web was fair game.
For the Lisp fans, Nyxt [2] is a decent choice as well.
Imagine you couldn't click on another tab with your mouse pointer while the current active one is loading. Yes, it's as terribly frustrating as it sounds.
In the XUL days I could even use vim shortcuts to access every button in the Firefox UI!
Luckily there is a solution for now. VimFx[1] is still being updated and works with the LegacyFox shim!
I like qb the most, as it's fairly stable and fully-featured. It offers full keyboard control, and many cool features like bindings for host-granular permissions for js and images, and is also scriptable. Built-in decent adblocker.
The main annoyance about it for me is it doesn't come with DRM, but it could also be seen as a feature, because it saves me a lot of time I'd otherwise watch arguably crap content.
Yes, but neither support extensions AFAIK. Not ready to take my browsing back to a pre 2004 era. :)
I've never experienced your problems, Vimium works on any tab, indipendently from the others.
I don't understand your glitches, really.
Joking aside, I’ll have to give this extension a spin.
Vimium is not a Bowser on its own. Not yet at least.
It certainly doesn't look like a turtle.
It would be interesting if Chrome let you point an extension to a github repo (and tag or commit hash) and pull source from there.
You lose automatic updates though.
Sometimes I feel like the only reason it's not a platform-breaking problem is that most extension devs make enough money from their day job to not care about a quick buck.
FWIW I tried the vimium or vimperator before and found it clunkier than I expected, so I can believe qutebrowser is better.
For example, qutebrowser supports a hinting mode where I press Enter to activate a link after selecting it with hints, which almost entirely eliminates accidentally clicking the wrong link, something I still do occasionally with Vimium+Firefox.
It is also much more scriptable, so I can for example create a keyboard binding for clipping selected text (with references) directly to my localhost pastebin.
Every action you can imagine is scriptable and bindable.
It has built-in support for adblock and granular JS/image/etc permissions.
Great keyboard-accessible bookmarking system.
Keyboard-accessible and reproducible settings and bindings with autocomplete and lookups.
Not to mention that it does not on a regular basis non-consensually take away features I use/introduce features I don't want and can't disable.
Clunky would be the exact term I find my day to day with these extensions - it's often pressing a key, noticing the focus is somewhere that makes the extension not catch it, and then either using a mouse or a key shortcut just to move focus somewhere the extension works with before repeating the actual command. I'd get so used to it that even when the keys do work I'm using them really slowly as I expect they might not. That never happens in qute, if I press a key it will work unless I've made a mistake myself. Also the UI being native Qt it feels snappier for me than extensions bolted on existing browsers.
The features qutebrowser can implement are somewhat limited by the web engine API and it doesn't have some things other browsers do, which is exactly why sometimes I try out these extensions, but usually after trying them for a day it feels so good to get back to qute and get an instant reliable response to key presses that I don't care about the few missing things.
The only configuration: I disabled it on banking sites... you never know.
To disable it, just press its icon on any website, and it will stay disabled on all the domain.