Servo vs Ladybird
thelibre.news

I believe that Ladybird has more funding and better support for the web, but Servo wins in performance. Though, they’re hard to compare directly!

  • asudox@lemmy.asudox.devEnglish
    611·
    8 days ago

    I don’t think Ladybird can compete with the other browsers with that speed.

    Oh and I still wonder why they chose Swift over all the other compiled languages to this day. Was OOP really that crucial?

    I’m waiting for Servo tbh.

    • Agosagror@lemmy.dbzer0.comEnglish
      28·
      8 days ago

      Primeagen interviewed the creator, who basically said they chose swift because it was fun. Other languages they tried were less fun.

      • isaacd@lemmy.worldEnglish
        7·
        6 days ago

        As a professional dev (okay, okay, forgot where I was, aren’t we all) I approve of this reasoning

    • sugar_in_your_tea@sh.itjust.worksEnglish
      15·
      8 days ago

      Swift is great! The guy who made Rust worked on Swift for 3-ish years, so there’s a fair amount of overlap in interest between the two. Those were the two main contenders, and I guess OOP was the deciding factor.

      I’m waiting for whichever is ready first.

      • jbaber@lemmy.sdf.orgEnglish
        19·
        8 days ago

        HN crowd told me they’re porting to swift. When I asked “why not Rust”, they said the C++ code was very OOP, so it was easier to port to swift.

        • taladar@sh.itjust.worksEnglish
          24·
          8 days ago

          Which probably means it uses deep inheritance hierarchies since that is the one thing that does not exist in Rust (and for a good reason).

          • barsoap@lemm.eeEnglish
            1·
            7 days ago

            You can do deep hierarchies in Rust, the thing Rust doesn’t have is implementation inheritance. Or more precisely said implementation inheritance that relies on anything but the interface (traits can have default methods but they’re part of the trait definition, not any implementation).

            • taladar@sh.itjust.worksEnglish
              1·
              7 days ago

              Yes, most likely they use it for implementation inheritance which is sloppy anyway since it usually violates the Liskov substitution principle and also most OOP languages that have that concept tend to have issues around co- and contra-variance in either function parameter and return types or containers or both.