Vimium – The Hacker's Browser
github.com
Vimium – The Hacker's Browser
1–10 of 86 posts
Re: Vimium – The Hacker's Browser
#2Re: Vimium – The Hacker's Browser
#3Re: Vimium – The Hacker's Browser
#4It would be interesting if Chrome let you point an extension to a github repo (and tag or commit hash) and pull source from there.
Re: Vimium – The Hacker's Browser
#5Re: Vimium – The Hacker's Browser
#6I wish textareas had keybindings
Re: Vimium – The Hacker's Browser
#7Re: Vimium – The Hacker's Browser
#8This has been a great extension but i'm always nervous about Chrome extensions and their seemingly global access to everything and some dev's willingness to sell to malware devs. 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.
Re: Vimium – The Hacker's Browser
#9I've used this and other similar extensions but always them being an extension makes for a slow and unreliable experience imo. Pressing shortcut keys just might work depending on the focus and other current state. Going back to qutebrowser after trying out these extensions feels so fast and reliable in comparison - when you press a key it will instantly work like it should.
FWIW I tried the vimium or vimperator before and found it clunkier than I expected, so I can believe qutebrowser is better.
Re: Vimium – The Hacker's Browser
#10I've used this and other similar extensions but always them being an extension makes for a slow and unreliable experience imo. Pressing shortcut keys just might work depending on the focus and other current state. Going back to qutebrowser after trying out these extensions feels so fast and reliable in comparison - when you press a key it will instantly work like it should.
I just looked and qutebrowser is basically a webview right? I've played with webviews a little and it didn't feel much different than other injection-style scripting. What would make that better than the extension? FWIW I tried the vimium or vimperator before and found it clunkier than I expected, so I can believe qutebrowser is better.
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.