4 ms·
> mostly do some simple text-mangling If you call communication with two different browsers (at least), validating source code, signing code and packing it up
by diggan 6y ago
> mostly do some simple text-mangling
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. 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.
> Why do I have to install Node
Because web developers who do JavaScript for a living find it easier to write JavaScript to support their developer tools. Not a huge surprise here. 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 why rewrite something that works well enough for the intended users?
Speaking of cargo-cultism, you seem to have a bit of that stench on yourself as well, where suddenly every utility "should of course" be written in Rust, or otherwise be rewritten in Rust if they are not doing it yet.
Programmers will scratch their own itch with the languages that are familiar to them. Of course web extension dev tools will be written in languages and platforms that are the closest to the web ecosystem, which today is JavaScript.
- toyg 6y ago> communication with two different browsers (at least), validating source code, signing code and packing it up ... is not something that requires a massive engine like Node. It just isn't. > Because web developers who do JavaScript for a living find it easier to write JavaScript This is an argument I can accept from a random free-time-opensource developer, not from a well-funded behemoth like Mozilla. An org that big should pay attention to what their objectives are, not what they feel like hacking together on any given day. How can they not see that making this sort of tool significantly burdensome to install on 90% of desktops is bound to limit its impact? > suddenly every utility "should of course" be written in Rust No. Write it in Go if you prefer. Write it in brainfuck, I don't care. What I care about, as a user, is that I can just get a single executable I can run on my machine. I care about usability, that's all I care about. How can it be acceptable for a tool like web-ext to have a setup story that is "figure out how to install npm; npm install web-ext and see it fail; figure out how to install Visual Studio (will it even work with the free version? I hope so); re-do npm install web-ext, ignoring a bunch of warnings about everything being horribly insecure and unmaintained"...? And then they have the gall to say in their copy that "you only need a text editor", just before pushing this crap. I mentioned Rust only because it's terrible optics that its very home doesn't dogfood it. Again, not rocket science to notice, at organizational level. As a fervent Firefox advocate, this is the sort of thing that really riles me up.
- diggan 6y agoI think in your rage against nodejs and/or Mozilla, you forget the target audience of this tool. The tool is written and provided for and by web developers who write browser extensions. The extensions themselves are written in HTML, CSS and JavaScript and the web developers who do write extensions, unless they are first time web developers, for most parts have nodejs already installed on their machine. For them, installing and using web-ext is as easy as it is for you to pull down a binary and putting in $PATH, or installing a tool via your package manager. I maybe wouldn't have written web-ext in js with nodejs myself, but I do understand why others would make the choice to do so. Although I agree that the whole nodejs/npm ecosystem is just a insecure clusterfuck waiting to be properly exploited at this point. About the Mozilla objectives, I don't think they even know them themselves at this point, even less so around 2015 when this tool first appeared.
- toyg 6y ago> you forget the target audience of this tool. I understand, but the reality is that Chrome's own experience to do this sort of thing is still miles ahead. It's literally trivial to build a Chrome extension. It's a big part of Chrome's success: people who used to struggle to build FF extensions when it was about XUL and RDF, when Chrome arrived could quickly bang together something that directly improved their life. Google understood that their audience was anyone using a browser, not just this or that subset of markup fanatics. One of the pros of the Quantum switch was that building FF extensions became as easy as Chrome. Reintroducing complexity via the tooling is just self-harm.
- otterlicious 6y agoI guess you are thinking this tool is required because you are coming from Google Chrome extension development where you need a compiler tool to create CRX files. This is not the case for Firefox extension development. It uses plain ZIP files. You do not need this or any command-line tool to create Firefox extensions. You can create and publish an extension entirely with Notepad, Firefox, and the built in ZIP functionality of Windows Explorer if you want.