[cpeterso]

Phoenix/Firefox was Mozilla's own lightweight alternative to SeaMonkey. Then Chrome was the lightweight alternative to a memory-hogging Firefox. Now Chrome is seen as sluggish and a memory hog. Where do we go next?

[firasd]

I suppose, as far as the web platform is concerned, we aren't really going to replace HTML/CSS/JS so increasing the speed and memory management of javascript rendering is the clear way forward, e.g. with Servo https://www.mozilla.org/en-US/research/projects/

[wvenable]

Servo, when it's done. And from there, who knows!

[cpeterso]

btw, browser.html is a Servo experiment with "future UI paradigms":

https://github.com/mozilla/browser.html/

[Touche]

It says right on the page that it doesn't use Servo.

[Manishearth]

https://github.com/glennw/servo-shell does though

[frik]

I would like to switch to servo-shell sooner than later. Though there is no Win32/64 build of Servo.

See Servo github issue "Get Servo working on Windows": https://github.com/servo/servo/issues/1908

[cwyers]

Microsoft Edge?

[zanny]

There are a lot of alternative browsers, though almost all of them use Blink.

[hackmiester]

...back to Seamonkey? :D