6 ms·

Version 1.0.0 was released today, check it out! This is definitely the best hackable browser out there. It combines QtWebEngine and Python, which are incredibly

Version 1.0.0 was released today, check it out! This is definitely the best hackable browser out there. It combines QtWebEngine and Python, which are incredibly stable yet fast to develop in. It's a great alternative to what's left of the Firefox genocide of extensions, where only VimFX and Saka Key exist.

nextos 9y ago
A great successor to Vimperator is on the works now: https://github.com/cmcaine/tridactyl https://github.com/cmcaine/tridactyl
- StavrosK 9y ago
  Rather off-topic question: aren't WebExtensions meant to work on all browsers? I don't see either Chrome extensions working with Firefox 57 or the reverse.
  - jccalhoun 9y ago
    as I understand it webextensions are aiming to be a superset of chrome extensions.
    - The-Compiler 9y ago
      WebExtensions are a common extension format/API, i.e. Chrome extensions are WebExtensions. However, each browser vendor has their own specific additions, and hopefully Mozilla will add some things addons like Vimperator would need, see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061
    - sevensor 9y ago
      Shouldn't be a problem here, as QtWebEngine is Chromium.
  - vortico 9y ago
    Firefox and Chromium will never support full keybinding-driven navigation. WebExtensions severely limits when keys can be captured, so there are many cases where they cannot be used: when the addressbar is focused, while pages are loading, etc. Qutebrowser keybindings essentially have full control over the page at all times.
    - The-Compiler 9y ago
      FWIW some people from the Tridactyl project are working with Mozilla at getting a better keyboard WebExtension API for Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 It's going quite slow however...
  - 482794793792894 9y ago
    Some WebExtensions will work in all browsers. Other WebExtensions will only work in certain browsers that offer a capability that the extension needs. Kind of like webstandards have always worked. For example, Opera and Firefox support the Sidebar API, which allows essentially arbitrary HTML pages to be placed in, you guessed it, a sidebar. Chrome does not support this, because they supposedly just don't want to have sidebars in their browser (it's not exactly an unsolvable task to implement). Overall, Firefox will support the most extension APIs, but even there not all extensions will work, because there's always going to be some APIs that only make sense in one specific browser. Lastly, it is necessary for the extension authors to port their extension. The work they have to do for porting might often be as minimal as just repackaging, testing and then uploading to the other browser's extension webpage, but they do have to do it. So, this is going to cut off many extensions, too. If they're unmaintained, no one's going to port them. And Mozilla has much stricter policies for telemetry, ads etc. in extensions, too, so another chunk of extensions won't get ported for that reason. If there is a specific Chrome extensions that you care for getting ported and it's unmaintained, then you can try it with Chrome Store Foxified [1], which will do the repackaging automatically. The testing you'll have to do yourself and then the fixing of potentially broken things and uploading, that depends on the license of the extension, if you're allowed to do that. [1] https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/ https://addons.mozilla.org/en-US/firefox/addon/chrome-store-...
inyourtenement 9y ago
VimFX is dead.
- hannofcart 9y ago
  A shame really. VimFX is so critical for my workflow that I am not going to upgrade to FFv57 just because of this.
  - semi-extrinsic 9y ago
    FF Extended Support Release will provide bugfixes for v52 until June 2018. I've switched to it with Pentadactyl while hoping there will be a useable API for proper Vim plugins by then.
  - jrimbault 9y ago
    What's your typical workflow in your browser ?
    - hannofcart 9y ago
      I use VimFX on FF, i3-wm as my window manager and vim for writing code. It's mouse free nirvana.
- asmdev 9y ago
  Is there a good alternative for VimFx?
  - velkyel 9y ago
    vimium
  - The-Compiler 9y ago
    There's Vimium-FF and Saka Key at the moment: https://addons.mozilla.org/en-GB/firefox/addon/vimium-ff/ https://addons.mozilla.org/en-GB/firefox/addon/vimium-ff/ https://key.saka.io/ https://key.saka.io/ Also, Tridactyl is at the planning stage and working with Mozilla on a better keyboard WebExtension API: https://github.com/cmcaine/tridactyl https://github.com/cmcaine/tridactyl https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 edit: Oh, looks like Tridactyl has quite some code already. I'm not sure if it's runnable yet, though.
crispinb 9y ago
"Genocide"? Well there's a new low in English word usage.
- mort96 9y ago
  > The systematic and planned extermination of an entire group. Sure, technically it only applies to an ethnic/political/racial/etc group of humans, but it's not _that_ far-fetched to apply it to the systematic and planned extermination of an entire group of software (in this case Firefox add-ons).
  - pidg 9y ago
    First they came for Greasemonkey, but I did not speak out, because I was a Scriptish user...
  - Seirdy 9y ago
    It has some negative connotations worth disagreeing with, though. I for one am pro-Webextensions (WE) because the legacy APIs gave all addons unlimited privileges and kept Firefox internals from improving. WE apis have come miles; even Tree Style Tabs has a WE alternative. I am hopeful for Qutebrowser, though; the dev is working on an interesting approach to extending the browser without WE support by allowing "userscripts" (not the Greasemonkey-esque ones). They can be written in tons of different languages. [Relevant documentation](https://qutebrowser.org/doc/userscripts.html https://qutebrowser.org/doc/userscripts.html).
  - arthur_pryor 9y ago
    i think maybe we should keep "genocide" reserved for people, or at least wait on applying it to software till we think that software might be sentient. linguistic inflation sort of sucks [0]. [0] http://www.macmillandictionaryblog.com/is-linguistic-inflation-insanely-awesome http://www.macmillandictionaryblog.com/is-linguistic-inflati... ("linguistic inflation" is a term that i've been using in my own head for years without using it in conversation, so i'm glad to see others have the same complaint)
    - 9y ago
The-Compiler 9y ago
Quick update on that: I just released v1.0.1 which fixes some bugs introduced in v1.0.0: - Fixed starting after customizing `fonts.tabs` or `fonts.debug_console`. - Fixed starting with old PyQt versions compiled against newer Qt versions. - Fixed check for PyQt version to correctly enforce 5.7 (not 5.2).
jacek 9y ago
I am using Vimium-FF on Firefox 57. https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/?src=ss https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/?sr...

nextos 9y ago

A great successor to Vimperator is on the works now: https://github.com/cmcaine/tridactyl https://github.com/cmcaine/tridactyl

StavrosK 9y ago
Rather off-topic question: aren't WebExtensions meant to work on all browsers? I don't see either Chrome extensions working with Firefox 57 or the reverse.
- jccalhoun 9y ago
  as I understand it webextensions are aiming to be a superset of chrome extensions.
  - The-Compiler 9y ago
    WebExtensions are a common extension format/API, i.e. Chrome extensions are WebExtensions. However, each browser vendor has their own specific additions, and hopefully Mozilla will add some things addons like Vimperator would need, see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061
  - sevensor 9y ago
    Shouldn't be a problem here, as QtWebEngine is Chromium.
- vortico 9y ago
  Firefox and Chromium will never support full keybinding-driven navigation. WebExtensions severely limits when keys can be captured, so there are many cases where they cannot be used: when the addressbar is focused, while pages are loading, etc. Qutebrowser keybindings essentially have full control over the page at all times.
  - The-Compiler 9y ago
    FWIW some people from the Tridactyl project are working with Mozilla at getting a better keyboard WebExtension API for Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 It's going quite slow however...
- 482794793792894 9y ago
  Some WebExtensions will work in all browsers. Other WebExtensions will only work in certain browsers that offer a capability that the extension needs. Kind of like webstandards have always worked. For example, Opera and Firefox support the Sidebar API, which allows essentially arbitrary HTML pages to be placed in, you guessed it, a sidebar. Chrome does not support this, because they supposedly just don't want to have sidebars in their browser (it's not exactly an unsolvable task to implement). Overall, Firefox will support the most extension APIs, but even there not all extensions will work, because there's always going to be some APIs that only make sense in one specific browser. Lastly, it is necessary for the extension authors to port their extension. The work they have to do for porting might often be as minimal as just repackaging, testing and then uploading to the other browser's extension webpage, but they do have to do it. So, this is going to cut off many extensions, too. If they're unmaintained, no one's going to port them. And Mozilla has much stricter policies for telemetry, ads etc. in extensions, too, so another chunk of extensions won't get ported for that reason. If there is a specific Chrome extensions that you care for getting ported and it's unmaintained, then you can try it with Chrome Store Foxified [1], which will do the repackaging automatically. The testing you'll have to do yourself and then the fixing of potentially broken things and uploading, that depends on the license of the extension, if you're allowed to do that. [1] https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/ https://addons.mozilla.org/en-US/firefox/addon/chrome-store-...

inyourtenement 9y ago

VimFX is dead.

hannofcart 9y ago
A shame really. VimFX is so critical for my workflow that I am not going to upgrade to FFv57 just because of this.
- semi-extrinsic 9y ago
  FF Extended Support Release will provide bugfixes for v52 until June 2018. I've switched to it with Pentadactyl while hoping there will be a useable API for proper Vim plugins by then.
- jrimbault 9y ago
  What's your typical workflow in your browser ?
  - hannofcart 9y ago
    I use VimFX on FF, i3-wm as my window manager and vim for writing code. It's mouse free nirvana.
asmdev 9y ago
Is there a good alternative for VimFx?
- velkyel 9y ago
  vimium
- The-Compiler 9y ago
  There's Vimium-FF and Saka Key at the moment: https://addons.mozilla.org/en-GB/firefox/addon/vimium-ff/ https://addons.mozilla.org/en-GB/firefox/addon/vimium-ff/ https://key.saka.io/ https://key.saka.io/ Also, Tridactyl is at the planning stage and working with Mozilla on a better keyboard WebExtension API: https://github.com/cmcaine/tridactyl https://github.com/cmcaine/tridactyl https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 edit: Oh, looks like Tridactyl has quite some code already. I'm not sure if it's runnable yet, though.

crispinb 9y ago

"Genocide"? Well there's a new low in English word usage.

mort96 9y ago
> The systematic and planned extermination of an entire group. Sure, technically it only applies to an ethnic/political/racial/etc group of humans, but it's not _that_ far-fetched to apply it to the systematic and planned extermination of an entire group of software (in this case Firefox add-ons).
- pidg 9y ago
  First they came for Greasemonkey, but I did not speak out, because I was a Scriptish user...
- Seirdy 9y ago
  It has some negative connotations worth disagreeing with, though. I for one am pro-Webextensions (WE) because the legacy APIs gave all addons unlimited privileges and kept Firefox internals from improving. WE apis have come miles; even Tree Style Tabs has a WE alternative. I am hopeful for Qutebrowser, though; the dev is working on an interesting approach to extending the browser without WE support by allowing "userscripts" (not the Greasemonkey-esque ones). They can be written in tons of different languages. [Relevant documentation](https://qutebrowser.org/doc/userscripts.html https://qutebrowser.org/doc/userscripts.html).
- arthur_pryor 9y ago
  i think maybe we should keep "genocide" reserved for people, or at least wait on applying it to software till we think that software might be sentient. linguistic inflation sort of sucks [0]. [0] http://www.macmillandictionaryblog.com/is-linguistic-inflation-insanely-awesome http://www.macmillandictionaryblog.com/is-linguistic-inflati... ("linguistic inflation" is a term that i've been using in my own head for years without using it in conversation, so i'm glad to see others have the same complaint)
  - 9y ago

The-Compiler 9y ago

Quick update on that: I just released v1.0.1 which fixes some bugs introduced in v1.0.0: - Fixed starting after customizing `fonts.tabs` or `fonts.debug_console`. - Fixed starting with old PyQt versions compiled against newer Qt versions. - Fixed check for PyQt version to correctly enforce 5.7 (not 5.2).

jacek 9y ago

I am using Vimium-FF on Firefox 57. https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/?src=ss https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/?sr...