With all due respect, less than 0.1% of browser users likely feel that way.
Don't mean to discredit or invalidate your feelings, I just feel the need to disclaim that it's impossible to meet people's need with that granularity.
The alternative is that they keep XUL, make 0.1% of the install base happy, and ditch the performance increases that Quantum/WebExtension have given us... at which point there wouldn't be a NYT article and we'd all just be stuck in a browser monoculture.
I do not believe that was the only alternative. I have spent a lot of time reading bug reports / feature requests relating to this functionality, and it certainly seems that much of it could be enabled, but apparently never will. The developers seem to think that giving extensions "too much power" would be dangerous, and thus it is best not to let anybody choose power over safety guarantees.
It seems a little too harsh to bring up Linus Torvald's "If you think your users are idiots, only idiots will use it" quote, but it tends to come to my mind whenever I read the abovementioned discussions.
I used VimFX before and I'm using Vimium now. It's okay, but it works nowhere near as well as VimFX did. The biggest problem is that it doesn't work until a page has loaded. So if I open a page and while it's loading I want to open a new tab, I can't use Vimium shortcuts to do it.
Want a bind to open something in mpv/youtube-dl
`";v": "hint -W exclaim_quiet mpv"`
Want to open a text field in gvim? Hit `ctl+i`
Want to remove the extra chrome: run `:guiset gui none`
I stuck on the ESR of firefox for a long time because I wasn't willing to give up vimperator. Its not the same, but its pretty close. There are 2 main pain points, which I don't know it will be possible to address. First the page has to before its functional. Second currently domain keybinds take priority (looking at you github).
You know how mathematicians get excited by exp(-i*pi)+1=0? This is like that but for all of the things I'm embarrassed about in Tridactyl:
- our documentation is not great, particularly of current configuration/possible configurations, hence why the GP didn't know about it
- hints don't support pipes - obviously this should be `hint | ! mpv`
- hints don't support pipes because of a bad architectural decision: we have most stuff living in a background script, when really we should probably have most stuff run on the web page where all the objects live, so that passing them around is easier
- we don't have an argument parser, so silent versions of commands have to be separate functions
...but I'm very glad you like it!
Regarding your pain points:
1. Tridactyl actually works really soon after the page starts loading, but only for commands that don't add UI. Personally I use quickmarks to escape from slow loading pages. Otherwise, this will probably never be fixed.
2. This isn't actually true. Tridactyl does override page binds. The reason you think GitHub is stealing a Tridactyl bind is because GitHub steals `/`, but Tridactyl doesn't bind anything to `/` - that's a default Firefox bind! (And whoever decided it would be a great idea to use that in GitHub should probably test their code in more browsers).
Yeah Tridactyl is great. While I'm not a great JS/TS developer I might be able to offer a couple of pull request for documentation. Is there anything I can help with currently?
> 2. This isn't actually true. Tridactyl does override page binds. The reason you think GitHub is stealing a Tridactyl bind is because GitHub steals `/`, but Tridactyl doesn't bind anything to `/` - that's a default Firefox bind! (And whoever decided it would be a great idea to use that in GitHub should probably test their code in more browsers).
The next big win in documentation is configuration docs, but there's a type doc bug I'm waiting on first before I can merge it.
However, the `tutor`, new tab page, help page introduction and addons.mozilla.org page (stored on repo as amo.md) always fall out of date, so time spent reading through those and adding things that are missing or out of date is always time well spent. The changelog is probably the easiest source of truth to work from.
WOW, thanks for this! This extension is awesome. This provides all the functionalities I use vimium (in chrome) for, but what does it for me is this:
> Want to remove the extra chrome: run `:guiset gui none`
Top bar with so much padding is one of the main reasons I am not using Firefox.
Also the awesome command bar at the bottom is something that I've always found missing in vimium, (which has an omnibar but it's placing feels awkward.)
Can native message fix the fundamental problems in keyhandling? Meaning it can react to keys without the site fully loaded? Work on all sites and dialogs? Have a predictable behaviour instead of timing-problems which can happen now if you type to fast? For example, opening the commandline and typing something to fast can have the effect that the typed text does not end in the commandline but instead is handled outside of it.
