Firefox was never intended a better lynx; hating on Mozilla for that is a bit ridiculous. Have you considered using surf or xombrero?

That's technically true, but before it was firefox (before it was Firebird, even), It was intended very much as a stripped-down gecko frontend written in XUL, much closer to Lynx than the firefox we all use today.

Servo is very similar in useability to lynx right now, if grandparent is interested in trying it out.

Stripped-down compared to the Mozilla Suite, which came with an email client and HTML editor, but the browser itself was intended to match and extend the Mozilla featureset.

this is very much not true. Phoenix was not intended to extend the featureset.

From the release notes of Phoenix 0.1:

> Not only does Phoenix aim to match the featureset of Mozilla -- subtracting features deemed geeky and better offered as add-ons -- but it extends it. For example, it adds customizable toolbars and quicksearch in bookmarks and history. It will soon offer an add-on manager, a better wallet, and a new downloads sidebar pane.

http://website-archive.mozilla.org/www.mozilla.org/firefox_r...

Yeah, it was really nice when it didn't have the add-on manager yet. just a small, XUL-based browser. Made me switch from Galeon.

Still didn't ever complete the suite, though; Thunderbird tackled email, Sunbird handled contacts. Good thing, too; Seamonkey was a pig on my pentium 133 w/32MB RAM. Played quake fine, but just couldn't handle Seamonkey. Phoenix got me extra life out of my ancient hardware.

These days, Xombrero is getting me the same sort of extra life out of my ancient (or otherwise under-powered, e.g. Raspberry Pi) hardware. It's a very light frontend to GTKWebKit with a glorious vi-like UI.

Now I wonder if it would be worth making something similar in XUL...

that's what I signed up for, back when it was Phoenix. These modules were supposed to be optional.

however, merging Torbrowser is something I can support; everyone automatically gets a privacy upgrade, and the web stays open as a result.

I imagine adding the feature of a one click javascript disable would cost a lot of money to mozilla. I wonder how much? That is a very honest question.