5 ms·

Have a read about Servo, it is binding with SpiderMonkey as JS engine. Is there some chance, that servo decomposed from SpiderMonkey? If it is not, I don't thi

• culi 2y ago
  There's a lot more to a browser than the JS engine. And in general, we would want all of the browsers JS engines to be essentially the same. I think starting with an existing engine is the most logical approach
  • abhinavk 2y ago
    True but at this point of time, Firefox and Servo are using the same CSS engine, same JS engine and same compositor and rendering engine.
    • fabrice_d 2y ago
      That still leaves you with at least the layout engine, all the DOM apis, all the networking, multi process model & sandboxing, web extensions support, that are different implementations.
  • akira2501 2y ago
    > we would want all of the browsers JS engines to be essentially the same You say until there is a CVE found.
  • tvshtr 2y ago
    They plan to abstract it (work is underway) to make it even possible to use chromium's js engine. https://www.phoronix.com/news/Servo-JavaScript-Engine-Modular https://www.phoronix.com/news/Servo-JavaScript-Engine-Modula...
    • culi 2y ago
      Interesting. Kinda reminds me of the 360 Safe browser that's one of the most popular browsers used in China. It can render a website using WebKit, Blink, or Trident (Internet Explorer)
      • niutech 2y ago
        It's not about including multiple web engines (like e.g. Sleipnir does) but multiple JS engines in a single web engine.