Announcement

Collapse
No announcement yet.

Servo Continues Making Progress For Shipping Components In Gecko, Browser.html

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Servo Continues Making Progress For Shipping Components In Gecko, Browser.html

    Phoronix: Servo Continues Making Progress For Shipping Components In Gecko, Browser.html

    Mozilla's next-generation, written-in-Rust Servo browser layout continues making progress as well as on the browser.html front-end and their goal of shipping at least one or more Rust/Servo components within the Gecko engine currently powering Firefox...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    What's next, implement the browser engine itself in javascript?

    Comment


    • #3
      Why don't they move away from XUL and embrace GTK?
      Is it because they must then embrace GTK, Windows Forms and Cocoa at the same time, and its much effort?

      Comment


      • #4
        Originally posted by uid313 View Post
        Why don't they move away from XUL and embrace GTK?
        Is it because they must then embrace GTK, Windows Forms and Cocoa at the same time, and its much effort?
        browser.html is a move away from XUL, but towards HTML …

        Comment


        • #5
          Michael - thanks for the link to the This Week in Servo blog. Cool.

          Originally posted by uid313 View Post
          Why don't they move away from XUL and embrace GTK?
          My guess is security. They already have to do a lot of security work around HTML and Javascript, period. So implementing as much as possible of the browser user interface in HTML and Javascript means that there should be fewer security holes in Servo in the user interface layer.

          If they use GTK, or Qt, or anything else that's a native graphical toolkit then they have to security audit and constantly update that too.

          Comment


          • #6
            Originally posted by Michael_S View Post
            Michael - thanks for the link to the This Week in Servo blog. Cool.



            My guess is security. They already have to do a lot of security work around HTML and Javascript, period. So implementing as much as possible of the browser user interface in HTML and Javascript means that there should be fewer security holes in Servo in the user interface layer.

            If they use GTK, or Qt, or anything else that's a native graphical toolkit then they have to security audit and constantly update that too.
            GTK or Qt doesn't require much in terms of security historically but focusing their attention on building the UI in what they already know best, makes sense anyway.

            Comment


            • #7
              Originally posted by RahulSundaram View Post
              but focusing their attention on building the UI in what they already know best, makes sense anyway.
              Except for the fact that html is about the worst ui description language right after assembly and ascii art.

              Comment


              • #8
                Originally posted by khagaroth View Post
                Except for the fact that html is about the worst ui description language right after assembly and ascii art.
                Except that millions of people are already using web applications written in a combination of html+css+js. Nothing new here.

                Comment


                • #9
                  Originally posted by khagaroth View Post
                  Except for the fact that html is about the worst ui description language right after assembly and ascii art.
                  HTML5 +javascript +css says Hi.

                  Comment


                  • #10
                    Originally posted by khagaroth View Post
                    Except for the fact that html is about the worst ui description language right after assembly and ascii art.
                    Maybe they could use XHTML5 instead of HTML.
                    Or some XML such as XAML.

                    Comment

                    Working...
                    X