Vimperator is not dead : use the browser Waterfox-classic

[JulioJu]

Issue type:

• Version compatibility

Version:

Thunderbird 68 and Waterfox 68 (based on Thunderbird 68) depreciated lot of XUL API. See https://developer.thunderbird.net/add-ons/tb68 and https://github.com/MrAlex94/Waterfox/wiki .

Just for confirmation. This changes means that Muttator for Thunderbird and Vimperator for Waterfox are dead ? First of all, I not see any solution to deactivate Electrolysis (es10) (see https://github.com/vimperator/vimperator-labs/issues/211) . It seems that browser.tabs.remote.autostart has disappeared in Config Editor / about:config .

Maybe lot of change in the plugin could save the plugin. But probably too much…

So sad… As Tridactyl is actually so far of Vimperator. Less functionalities, less ergonomic…

End of History…

[maxauthority]

Yeah, sad but true. :(

It's still good that other add-ons still at least try to bring the Vim spirit forward, even though not as advanced as the XUL-based Vimperator.

It was still such a nice project, and so much fun working with everybody involved.

-- Martin

On Wed, Jun 12, 2019 at 10:15 PM Julio notifications@github.com wrote:

Issue type:

• Version compatibility

Version:

Thunderbird 68 and Waterfox 68 (based on Thunderbird 68) depreciated lot of XUL API. See https://developer.thunderbird.net/add-ons/tb68 and https://github.com/MrAlex94/Waterfox/wiki .

Just for confirmation. This changes means that Muttator for Thunderbird and Vimperator for Waterfox are dead ? First of all, I not see any solution to deactivate Electrolysis (es10) in Vim (see #211 https://github.com/vimperator/vimperator-labs/issues/211) . It seems that browser.tabs.remote.autostart has disappeared in Config Editor / about:config .

Maybe lot of change in the plugin could save the plugin. But probably too much…

So sad… As Tridactyl is actually so far of Vimperator. Less functionalities, less ergonomic…

End of History…

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vimperator/vimperator-labs/issues/825?email_source=notifications&email_token=ABNUDL7QZKOOQT3GEJ2MEKTP2FKONA5CNFSM4HXQ6E72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZE5BUQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNUDL5QZHFOJDGU2B3LNBDP2FKONANCNFSM4HXQ6E7Q .

[mentalisttraceur]

@maxauthority @JulioJu : Vimperator is still alive for users on Pale Moon, which has no plans of deprecating XUL.

There is definitely an active minority of web users using Pale Moon - it even shipped as the default browser in the latest Manjaro Linux (i3 flavor) image I downloaded last week.

I originally passed over Pale Moon "as just another Firefox fork", thinking it would inevitably fall behind, but it seems to be doing... well, while it is behind on some modern web stuff like WebRTC, some HTML5 stuff (see a recent html5test.com result for it here), it is actively being independently developed (not just trying to merge code from upstream), and they do have a history of adding features like that since their fork.

So I'm currently feeling out using Vimperator on Pale Moon as my daily driver browser at work (because Qutebrowser struggles on Windows, and modern Firefox with Tridactyl has a couple of intolerable pain points for me).

So it's not dead for everyone, and even if you give up on it, I predict it will have some users for a long time.

[gkatsev]

Vimperator is dead only in as much as there isn't currently anyone to maintain it. If people use it on Pale Moon, that's awesome. Hopefully, someone steps up to maintain it, otherwise, it's just going to atrophy.

[JulioJu]

@gkatsev thanks so much to say me that Vimperator works with Palemoon ! Probably API of PaleMoon are improved, because in the past Palemoon not works https://www.reddit.com/r/palemoon/comments/6ehujp/vimperator/

[JulioJu]

@gkatsev works also with basilisk ! And works better with basilisk than with palemoon !

[neg-serg]

basilisk

Do you really think this is a better option than watefox?

[JulioJu]

basilisk

Do you really think this is a better option than watefox?

Waterfox will kick off compatibilitiy with Vimperator. Actually, Waterfox is still the best solution, but in some days or weeks, Basilik will be the only solution.

[JulioJu]

Maybe you already know, Waterfox keep the compatibility with classic add-ons, contrary that I have said. Actually, there is two Waterfox. A Waterfox that keep the compatibility with old add-ons like Vimperator, it is based on Firefox 56. And a Waterfox that kick-off compatibility of old add-ons, based on Firefox 68.

Waterfox is better than Basilisk and Palemoon, because it is base on a more recent version of Firefox and not hesitate to merge new features of Firefox based on Servo with the Rust language, if possible.

[JulioJu]

@gkatsev maybe this information could be write on the README.md of Vimperator ?

[smnthermes]

while it is behind on some modern web stuff like WebRTC

Google WebRTC is intentionally not included, since it's bad for privacy/security. However, Basilisk, which uses the same rendering engine, supports Google WebRTC. The same also applies to Google WebDRM (or Google WebWidevine).

some HTML5 stuff

Pale Moon/Basilisk are lacking Google WebComponents, but this is already being worked on. Some items such as WebVR and Gamepad control aren't relevant.

[smnthermes]

Waterfox is better than Basilisk and Palemoon, because it is base on a more recent version of Firefox and not hesitate to merge new features of Firefox based on Servo with the Rust language, if possible

LOL, there's nothing special about Servo and Rust. Also, Pale Moon and Baslisk receive frequent security and web compatibility updates.

[mentalisttraceur]

@smnthermes

WebRTC is intentionally not included, since it's bad for privacy/security.

Implementing WebRTC without proper granular visibility and controls is bad for privacy.

Implementing it with the right defaults and ability to see and allow or disallow connections that a page is trying to make is strictly empowering over not having it at all.

Before calling something insecure, remember to separate the essential parts of it from the incidental limitations of the implementations of it that you have seen so far.e