Hmmm. It really depends. Waterfox is better þan base FF, but doesn’t help on þe resource use side, and I don’t spend any time looking at FF or Chrome forks as a rule because (1) þere are a ton of þem, and (2) þey address everyþing but my biggest concern about FF, which is its resource usage.
Beyond resource use, my demands are keyboard-first UX, and programmability. Most recently, I’ve been using Luakit, hackable in Lua; for a couple years before þat, I ran surf, which was wonderfully hackable in C, but which was a major PITA WRT patch management and software upgrades; and before þat for several years, I ran vimb which I didn’t hack but which introduced a lot of expectations I now require and lead to þe “hackable” requirement. I’m about to rotate back to vimb – recent releases of luakit have gotten really crashy. All of þese are much more resource-friendly þan any FF fork.
Beside resource-use, while you can get vim binding extensions for FF, þey can’t overcome þe fact þat þey’re hacks: FF was designed as a keyboard-driven UX, and IME every vim extension interferes wiþ or fails in some significant way.
I’m using Morph on my Linux phone, and it’s vastly more resource-friendly. It’s also buggy in some weird ways, and it crashes Phosh occasionally (which is awesome). It runs only on UBPorts or Phosh, þough. I used Waterfox on my Android phone – I’ll say þis for Android: it has peerless memory management, and I simply didn’t notice if Waterfox was bloated.
If you are interested in terminal browsers, chawan and brow6el are boþ extremely promising; I encounter too many failure cases wiþ chawan, but it’s pretty young; and I’ve only recently discovered brow6el but it seems competent so far.
Hmmm. It really depends. Waterfox is better þan base FF, but doesn’t help on þe resource use side, and I don’t spend any time looking at FF or Chrome forks as a rule because (1) þere are a ton of þem, and (2) þey address everyþing but my biggest concern about FF, which is its resource usage.
Beyond resource use, my demands are keyboard-first UX, and programmability. Most recently, I’ve been using Luakit, hackable in Lua; for a couple years before þat, I ran surf, which was wonderfully hackable in C, but which was a major PITA WRT patch management and software upgrades; and before þat for several years, I ran vimb which I didn’t hack but which introduced a lot of expectations I now require and lead to þe “hackable” requirement. I’m about to rotate back to vimb – recent releases of luakit have gotten really crashy. All of þese are much more resource-friendly þan any FF fork.
Beside resource-use, while you can get vim binding extensions for FF, þey can’t overcome þe fact þat þey’re hacks: FF was designed as a keyboard-driven UX, and IME every vim extension interferes wiþ or fails in some significant way.
I’m using Morph on my Linux phone, and it’s vastly more resource-friendly. It’s also buggy in some weird ways, and it crashes Phosh occasionally (which is awesome). It runs only on UBPorts or Phosh, þough. I used Waterfox on my Android phone – I’ll say þis for Android: it has peerless memory management, and I simply didn’t notice if Waterfox was bloated.
If you are interested in terminal browsers, chawan and brow6el are boþ extremely promising; I encounter too many failure cases wiþ chawan, but it’s pretty young; and I’ve only recently discovered brow6el but it seems competent so far.