![]() But why rewrite something that works well enough for the intended users? I'm sure if you find the time to write the "simple text-mangling" in Rust, support it and maintain it, people would be more than happy to use it. But I'm quite sure many see those features as a bit more than that, hence it is quite a popular tool to use in conjunction with browser extensions.īecause web developers who do JavaScript for a living find it easier to write JavaScript to support their developer tools. ![]() If you call communication with two different browsers (at least), validating source code, signing code and packing it up "simple text-mangling", I understand you're a bit frustrated. I opted for a much simple option: with Chromium-based browsers, you can enable the extension-developer mode, and then you're allowed to load local extensions from the normal extensions page. I had the choice between loading each local extension after launching a new Firefox, which mean a dozen of clicks, or installing web-ext in order to sign my extensions, and sign them again after each change (no idea if there were extra actions needed in the process, like manual reload). Unfortunately, Firefox removes local extension when it closes. Then I discovered the secret debug-extensions page of Firefox where I could load them. The extensions page cannot load local extensions. After a Firefox update, they were not allowed anymore, because they're not signed. I have a few web extensions I wrote in order to customize a few web sites (automate tasks, alter display, etc). In my opinion, Firefox imposes complex constraints on casual developers, and web-ext is part of it.
0 Comments
Leave a Reply. |