3 ms·
I think emphasizing Servo is the wrong goal. Ideally, when rewriting a large legacy app you want to take the StranglerApplication[1] approach. Netscape tried r
by Ygg2 10y ago
I think emphasizing Servo is the wrong goal.
Ideally, when rewriting a large legacy app you want to take the StranglerApplication[1] approach. Netscape tried rewriting its software from scratch and we all know how that ended for Netscape[2] - Netscape is no more. Luckily, Firefox came from that whole mess. But I assume a lot of effort was lost, going from Netscape to Firefox.
In idealized scenario, Servo slowly starts taking replacing parts of Firefox. First URL parser and media player, then slowly DOM, CSS, Renderer, and finally takes over and rewrites JS VM.
The takeover is silent and gradual and user doesn't notices anything outside speed improvements. It's like some kind of silent Borg infection.
[1] http://paulhammant.com/2013/07/14/legacy-application-strangulation-case-studies/ http://paulhammant.com/2013/07/14/legacy-application-strangu...
[2] http://www.joelonsoftware.com/articles/fog0000000027.html http://www.joelonsoftware.com/articles/fog0000000027.html
- cgag 10y agoI think the user needs to notice a lot of improvements, at all at once, because firefox really feels hopeless at this point. I don't know though, maybe a slow turnaround will work, or a sudden rendering integration will be the turn around it needs.