Comment by classichasclass
8 years ago
I'm aware of Servo. Servo is neat to play with, though it's pretty bad with older legacy HTML pages. Also, I'm not sure how likely Mozilla is to develop it into a product; it seems more like a testbed for later Gecko evolution (which, to be sure, is still a good thing).
> I'm not sure how likely Mozilla is to develop it into a product
It's unlikely to become a standard desktop browser, but the roadmap [1] does mention investigating options like a standalone mobile browser [2] or perhaps to be used embedded in an app, e.g. for packaged web apps.
[1] https://github.com/servo/servo/wiki/Roadmap [2] https://github.com/servo/servo/issues/20855
Firefox already includes parts of Servo, so it’s not a question of “how likely” it is to be used in production. https://en.wikipedia.org/wiki/Quantum_(Mozilla)
> so it’s not a question of “how likely” it is to be used in production.
I believe you misunderstood the comment unless it was changed. The commenter questioned the likelihood of it being developed into a product and you responded as of they had questioned the likelihood of any of it being used in production.
Fwiw, I agree with the commenter and am unsure how likely Mozilla is to develop it into a product. They do seem to incorporate pieces though.
I think you and the commenter share some misunderstanding. Could you distinguish what you mean by developing Servo into a product vs. “incorporating pieces”?
Are you saying that Mozilla eventually replacing Gecko’s style system, DOM, compositor, and networking system with Servo’s (as the article I linked describes) is just incorporating “pieces” of Servo?
The product that Mozilla is developing Servo into is Firefox. I don’t know what you expect—for Mozilla to replace Gecko with Servo all at once? For Mozilla to do the same thing they are doing now but just give it a new name?
2 replies →
That's not what I meant. I meant whether Servo the engine is likely to be a standalone product (on its own merits along with Gecko).
I think you misunderstand what a browser engine is, then—read the Wikipedia article I linked and tell me how the “stand-alone product” that Servo is going to be is not Firefox itself. Massive parts of Gecko have already been simply deleted from the codebase and replaced with components from Servo.
“Firefox” is not a browser engine, it is a browser UI. Gecko and Servo are browser engines.