“Why should I use Nyxt if I can use Vimium?”
nyxt.atlas.engineer
nyxt.atlas.engineer
Also, the configuration format doesn't make it particularly easy. I don't want to learn LISP so that I can set my proper keybindings. Granted, I'm not fan of the vim language itself but it's pretty easy to set config with it.
I could imagine an extension that's modal and allows its own plugins to be written in JS and then loaded. This doesn't seem at all to be a fundamental limitation, just "Vimium et al aren't designed this way."
Similarly, couldn't an extension use Web Workers to do the intensive processing tasks without blocking rendering, with the only on-main-JS-thread actions being bridging the Web Workers to the DOM?
I guess extensibility is much easier with CLOS methods than with... however people write extensible programs in JavaScript. Prototype hackery? But one could again port CLOS methods to JS as a library, so that's not a fundamental limitation either, IMO. (Maybe the fundamental limitation is the JIT being able to optimize them? I think a normal method cache on the GF might work, though I'm unfamiliar with how JS engines optimize indirect calls in general.)
Currently yes. When Chrome eventually mandates Manifest V3 extensions, they will no longer be able to run code not contained in the signed extension package.
https://developer.chrome.com/docs/extensions/mv3/intro/mv3-m...
It's hard to live with many of those plugins. — Though I very much loathe that the plugins do not work on “special pages” which have to be navigated in an inconvenient manner.
This is one of the worst things about the Quantum addon changes in Firefox too. Can't use my Vimium shortcuts or Gesturefy gestures on a new tab page, nor on an error page (404 etc.), not even on a plaintext web page (i.e if the mimetype is text). It's so annoying and interruptive.