1. 26
  1. 3

    The screenshot provided on the kickstarter page looks awfully similar to what you’d see with vimium, the chrome extension. Not sure I’m convinced that a new browser could beat a well tuned chrome + vimium configuration

    1. 11

      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.
      1. 4

        Perhaps you can add these points on Kickstarter page as well?

        All the best for campaign!

    2. 2

      I love the idea behind qutebrowser, but it unfortunately still crashes too often, causing me to revert to chromium.

      1. 5

        What backend are you using (see :open qute:version)? With the last qutebrowser release and either the QtWebKit-NG (only packaged on Archlinux currently, as qt5-webkit-ng - and there’s a Gentoo ebuild) or the QtWebEngine backend (based on Chromium, you’ll need to start qutebrowser with --backend webengine, but with the new config there’ll be an option for it), I haven’t seen crashes in a long time.

        1. 1

          Actually, since I wrote that comment I opened up qutebrowser and am pleasently surprised to report that it has not crashed in the past three hours. I had previously used the webengine backend but still had major stability issues, even while running of the qutebrowser-git package from the AUR, just two or three ago. Hopefully it’s stable enough to become my daily driver now. Keep up the good work! :)

          EDIT: 3 more hours later, I’ve had it crash 3 times. Seems to struggle when my shitty internet connection suddenly goes away.

          1. 2

            Ouch. You’re most likely running into this Qt bug then.

            Currently qutebrowser still creates a QNetworkAccessManager even with QtWebEngine as it’s needed for some kinds of downloads (like the adblock lists). I want to convert those places to use the QtWebEngine/Chromium network stack as well, but QtWebEngine is still missing an API to do arbitrary downloads.

            Either way, qutebrowser can probably avoid creating a QNAM if it’s not needed, so this Qt bug doesn’t happen until a QNAM is needed in some way, at least. I opened an issue for that now.

      2. 2

        I’ve been using qutebrowser occasionally and can recommend it, the only thing that makes me come back to a more and more buggy vimperator is uMatrix and, ironically, mouse gestures.

        Even though I’m not really interested in the new configuration system, I’ll pledge when I’m home to keep up the momentum of the project.

        1. 1

          uMatrix (see the related issue) is something I plan to tackle once there’s a plugin API. It’s definitely something I want too, I have it installed in Chromium (but rarely use Chromium). The new config is a first step in that direction, which will at least allow to block e.g. javascript for a given domain.

          Mouse gestures would probably be possible to do as a plugin as well then, but I’m not going to be the one to write that plugin :D

        2. 1

          I know this probably relates to the plugin API that was mentioned, but how likely on a scale of 1-10 is getting AgileBits to create a 1Password extension for qutebrowser?

          1. 1

            I looked at their thread for an official Python API - 4.5 years old, and with this response:

            Unfortunately, I’m not sure that we will ever have an API for 1Password. There are some security concerns here: opening the door to another application or script could provide a mechanism for a malicious script to send users’ data to a third party. If there were a secure way to implement something like this, our developers would certainly consider it.

            With that, my hopes of something official are… pretty low. However, there’s an unofficial Python API - if that works, with the planned plugin API it should be a piece of cake to write a plugin for this.

          2. -1

            I love git, but I’m getting more and more annoyed by the phrase: A version control system like git

            1. 2

              Read it like so: […] a version control system, like Git or Mercurial or SVN or Perforce or Fossil or CVS or DARS or Bazaar or Sharepoint or Dropbox-which-lets-you-restore-older-versions-of-files-so-lets-use-that.

              Sorry about those last two. I wish I could say I had never seen them used where a version control system like Git should have been used. :-| ;-)

              1. 2

                Why so?

                1. -2

                  Git has about a million usage patterns and is - at it’s core - a blob store.

                  That phrase mostly transpires that the developers don’t have a good idea about what they will actually build and so just use this phrase.

                  It’s the tech equivalent of “like uber, but for genetically engineered easter bunnies”

                  1. 3

                    We’ll have to disagree then ;) I know very well how git works internally, but I’ve yet to see it being used somewhere as something other than some way of version control (or backup, which boils down to the same). Hell, even its own website starts with “Git is a free and open source distributed version control system”.

                    1. 1

                      Never used Gollum (Github wiki)?

                      But even as a version control system, git has a myrad of ways to be used as a version control system, of which some popular might or might not match to what your $product does.

                      My point was that “the git of X” is a bad description of most Xes, because Git is a very specific implementation of a concept.

                      1. 2

                        You do realize the original sentence was “[a file] which can be managed in a version control system like Git”, with Git being an example for a VCS - and not “X is like Git”?