I’ve used Vimium for some months myself, and wasn’t really happy with it. The reasons why mainly boil down to how Vimium is quite limited in what it can do. For example:

• It can’t change the user interface at all - qutebrowser has a much more minimal UI.
• It can’t spawn external processes. In qutebrowser, you can simply hit ctrl-e while editing some text input, to edit it in e.g. Vim. Or you can use :bind ,v spawn mpv {url} to add a keybinding which spawns mpv with the current page, to watch YouTube videos in a real video player.
• As soon as you are on some special page (like the Chrome extension store, or the “new tab” page), it stops working, because it can’t intercept keypresses there.
• In general, qutebrowser is much more configurable and extensible. You can easily integrate it with shell or Python scripts via userscripts, and soon there’ll be a Python plugin API as well.

“Do The Right Thing,” perhaps? As far as what that means, I just assume he means (to developers) don’t use it, (to users) complain about developers using it/sway developers from using it, (and to the React developers) change the license to make React free software. Or something.

EDIT: On second thought, perhaps it’s an indication to do something with the FSF’s free software directory? https://directory.fsf.org/wiki/Main_Page

The problem is that the ecosystems are somewhat interwoven as people use node modules in their frontend code.

I’m not sure it really is a good way to filter low quality submissions. Some articles about Node can be quite interesting and apply to things outside of just node.js.

I agree that it would be a way to filter submissions, but to cast them all as low quality seems like you’re just biased against the entire framework and ecosystem.

Ouch.