> sacrificed […] in the name of performance […] SeaMonkey still maintains these classic features, but is unfortunately a memory hog. I mean, there might be a r

> sacrificed […] in the name of performance […] SeaMonkey still maintains these classic features, but is unfortunately a memory hog. I mean, there might be a relation? I went from IE to Netscape (edit: Or NS to IE?), to Firefox to Chrome, then tried every 1-2 years to switch back to Firefox and always returned to Chrome because it was so much faster. It was only 2-5 years ago (can’t remember exactly) when FF switched to fully multiprocess and stopped using their unique extension model, that I could finally start using FF again because the performance was finally on par with Chrome.