• LeFantome@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Well, they do not answer the question “what is Servo” by saying it is a web browser. They answer that it is a “rendering engine”.

      But ok, you might think the obvious thing to do with a “rendering engine” is to make a browser.

      I guess that is why they answer the question “what can Servo do for you?” as follows:

      “Servo can be used to build embedded applications with web technologies, such as kiosk interfaces and digital signage. At present, Servo is especially suited to applications that use WebGL or WebGPU, as well as CSS-based applications where the developer has control over how components are implemented. Servo’s layout engine can similarly be used as the basis for Rust-based native UI frameworks.”

      Maybe it is just me but “we are making a web browser from Servo” or even “YOU could make a web browser with Servo” seem to be markedly under-represented in those answers.

      These are from the pages linked.

      I guess my question back would be, “what evidence is there that Igalia plans to make a browser?”.

      • anlumo@feddit.de
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Writing a browser not based on Blink or Gecko seems to be an insane goal these days. Maybe they don’t want to be insane.

      • jet@hackertalks.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Setting manageable expectations for the team, is a good thing. And yes a rendering engine can be the core part of a browser. And that is a massive huge monumental chunk of work. If they have the rendering engine production ready some team may be tor is going to wrap a browser interface around it. Getting the engine working is probably 90% of the work