qutebrowser vs vise

[ivanbalashov239]

Hi, this project were mentioned in qutebrowser's issue by @terlar
The question: Why are you developing vise on your own, and not contributing to the qutebrowser?
They are looks the same in technologies and ideas both.

for me there is a few unsolved issues with qutebrowser that stopping me from using it:

issue	qutebrowser	vise
site specific custom css	waiting to be implemeted in webengine	?
tree style tabs	could be implemented, discussed	the main feature

[kovidgoyal]

vise existed as a QtWebEngine based browser before qutebrowser decided to try porting to QWebEngine. And note that vise is really a personal project, I have never released it to the public (beyond uploading to github). I am not particularly interested in creating a general use product with vise -- that is much more work than making a browser that suits just my needs. And as I am already the maintainer of several open source projects, I dont really have the time to get involved with another at the moment.

[ivanbalashov239]

@kovidgoyal ok, thanks, that's understandable, but maybe you could mention what features of vise you miss in qutebrowser(it looks for me that, supporting vise even like personal product harder that using community driven qutebrowser)

[kovidgoyal]

Well, at the time I created vise, these were my main motivations:

1. Be based on modern chromium, multi-process engine
2. Be scriptable in python and/or a python like langauge like https://github.com/kovidgoyal/rapydscript-ng
3. Have a tab tree
4. Have a secure secret store based on files that could easily be synced using existing file sync tools
5. Be keyboard based
6. Allow easy access to the database of urls from other programs, so that you can, for instance, paste in a URL from the browsers history with just a few keystrokes while editing a file in vim

There were at the time no projects that met those needs, hence vise. I dont know what the current status of qutebrowser is, maybe it meets most of those needs nowadays.

Also, I find the effort of maintaining vise pretty trivial and completely worth it for a tool that is part fo my core workflow :)

[ivanbalashov239]

@kovidgoyal thanks, maybe you consider not cloning this issue, it could be informative for others, or mention it in the readme