• henfredemars
    link
    fedilink
    English
    arrow-up
    58
    ·
    8 months ago

    Ladybird faces an uphill website compatibility battle thanks to Chrome dominance. I wish them all the best.

    • Zetta@mander.xyz
      link
      fedilink
      arrow-up
      18
      ·
      edit-2
      8 months ago

      They are writing the browser from the ground up following web specifications, specifications Google themselves often write and maintain. So it should just work once it’s done, great talk by the lead Dev that goes into a lot more detail on that and just the project in general. https://youtu.be/9YM7pDMLvr4

      As far as I understand most websites load so far (slowly) and will be aout 90% correct, but with visual issues

      • henfredemars
        link
        fedilink
        English
        arrow-up
        16
        arrow-down
        1
        ·
        8 months ago

        I’m of the opinion that Google produces the specifications in bad faith, choosing features and constructions that are costly to implement to prevent others from entering the market. For example, see WebUSB. It’s a completely unnecessary standard at the very least and waste developer time. Other browsers have not bothered to implement it, generally calling it out for being a dumb specification.

        With that said yes there are standards, but primarily pushed and controlled by one company that is not interested in others writing web browsers. Hopefully they’re forced to divest themselves from Chrome.

        • Zetta@mander.xyz
          link
          fedilink
          arrow-up
          6
          ·
          8 months ago

          You seem to know more about it than I do, and I generally agree with your assessment. Either way ladybird has a talented team of paid engineers and tons of community contributors, so I’m choosing to believe in them even if Google is doing their best to stop them!

    • Ms. ArmoredThirteen@lemmy.zip
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      8 months ago

      Yeah I already can’t rely on just Firefox and keep chrome around as a last resort backup. I’ll be trying Ladybird out for sure though always good to help test new browser options

  • Venus_Ziegenfalle@feddit.org
    link
    fedilink
    English
    arrow-up
    45
    ·
    8 months ago

    Unlike other browsers, Ladybird is not based on Chromium or Gecko or Blink but on the new independent SerenityOS LibWeb engine with a Qt GUI.

    noice

      • x00z@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        8 months ago

        Why though? Qt is much easier for cross platform and cross DE development.

        libadwaita might be a good sideproject, but I don’t see much upside. And I even use Gnome.

        • Pirata@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          8 months ago

          Libadwaita just looks native on Gnome. I’m not saying its a necessity, but it would make the design feel more integrated on the system. I also run Gnome.

  • gravitas_deficiency@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 months ago

    That’s an awesome project.

    Question, though, from scanning the repo: why not rust? ~65% of the codebase is C++; strikes me that this’d be a FANTASTIC opportunity to show how incredibly efficient, effective, and safe rust can be for a wide-scale, consumer-oriented application.

    • feddup@feddit.uk
      link
      fedilink
      English
      arrow-up
      4
      ·
      8 months ago

      I think there was an interview where that question was asked and after various languages being evaluated it came down to being the language everyone working on it was most familiar with.

      I’m looking forward to using it in the future.

      • gravitas_deficiency@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        Well yeah, but be that as it may, greenfields are an opportunity for the contributors to dive headfirst into using a new language, and bring their expertise from other languages into that new one. Idk, that’s just how I look at it, given that this project doesn’t really have the feel of something that’s under serious time pressure.

        Edit: not to mention, I would be a little surprised if a lot of the js couldn’t be also replaced with rust compiled to WASM

        • feddup@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          I see your point and do agree greenfield projects can be great for learning new languages but only if the project is simple enough. Browsers are huge and complex, language choice is very important as well as who will be working on it.

          I think one of the arguments as well was that building the DOM in rust would have extra challenges as it’s fundamentally very object oriented so having a language suited to OOP would make it easier.

  • Pirata@lemm.ee
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    8 months ago

    I really hope something amazing comes out of this. Expectations are building up across many communities and I hope they can deliver.

    Still not sure how they will sustain themselves though. The donation model is obviously very ethical, but I doubt its sustainability in the long run.

  • nlgranger@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    8 months ago

    Shame they didn’t join effort on servo. AFAIK there is nothing wrong with it except for the fact they are not familiar with rust.