Slashdot Mirror
Pale Moon Devs Ponder Dropping Current Codebase And Starting From Scratch (softpedia.com)
An anonymous reader writes: The developers of the Palo Moon browser are thinking of scratching their current codebase due to the fact that it doesn't support many of today's current Web standards, and because future Firefox plans will introduce incompatibilities within its codebase. The team plans to build a new browser from scratch, which they'll use to replace Pale Moon when it reaches a stable version. As with the old Pale Moon, the browser will keep Firefox's pre-Australis interface and still support many features removed in Firefox, like Tab Groups and full themes.
I ran it in parallel with Firefox, mirroring every action, back when Firefox when firefox changed its UI: 300 tabs on each, playing videos and long text pages heavy css, and without closing for a few weeks.
The memory footprint was over a gig in PaleMoon-64s favour, and it wasn't showing any appreciable slowdown in performance. Can't speak towards Firefox nowadays, but I will note Pale Moon does seem to pick up a stutter with some videos lately if not shutdown. That could be entirely unrelated though.
This is basically what Debian does with Iceweasel (and Icedove). They pick a version of Firefox for the stable release (38 at the moment) and then just backport security fixes for it. For people that are just looking for a browser that doesn't change out from under them every time they start it, Iceweasel from debian stable is excellent.
Netscape 4 sucks, so lets throw it out and start again. Back when Spolsky could write he bitched about this.
Mozilla seamonkey sucks, so lets gut most of it and make Phoenix (now known as Firefox)
And now this again?