Every time I hear about Servo, it mostly can be boiled down to:
A: We did a ton of work
B: We're not even remotely close to something really useful yet
I think that says more about how websites work, to be honest.
A: We did a ton of work
B: We're not even remotely close to something really useful yet
I think that says more about how websites work, to be honest.
(In any case, I think the complexity is fundamental to many of the specs involved.)
Edge should, in principle, support everything, including legacy sites (at least as well as other browsers do today). Trident is only being kept around for sites that do extensive UA sniffing and rely on obscure behaviour — and pretty much only for the intranet.
I guess you could run two browser engines -- one for the UI, one for the content, but I'm not sure how well that would work.
The sheer amount of work involved in getting Servo to a usable state should be less surprising when you consider that all of the browser engines in current use date back to the 90s in some form (1997 for Gecko and Trident, 1998 for KHTML/WebKit/Blink).