• LeFantome@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    Don’t get me wrong, I am very excited by the possibility of having an independent browser engine. Firefox was that. Mozilla as an organization has compromised that. I hope Ladybird can avoid the same issues.

    The rationale for SerenityOS beyond therapy and fun was precisely the “being responsible for everything ourselves” aspect of the project. Andreas has previously described it as a form of accountability. He has also described it as a kind of freedom in contrast to the Linux model with its inevitable politics, bike-shedding, and inefficiency as you try to get dozens of projects to agree on direction and merge code. Ultimately, the mono repo allowed the project to do things right in the right place in the stack ( in the code ). It allowed the project to move quickly, to avoid legacy, and to continuously improve and modernize. It allows harmony across the entire developer AND user experience.

    Linux is famously fragmented. There is no open source desktop OS that provides “whole system” design and user experience harmony. Haiku comes close but it has never gotten much native app momentum. On Haiku, you are going to run the Falkon browser, use GIMP, and run LibreOffice. None of those are developed in concert with the OS.

    SerenityOS held the promise of Ladybird, and Hack Studio, and the userland utilities ( and everything else ) all being developed in concert. The same GUI toolkit was used for everything. The same standard library. The same error handling and code level security measures.

    This was the “need or use case”. Not anymore.

    And it is not just SerenityOS. Ladybird is not as independent as it was. Not just the sponsorships but the code. SerenityOS is no longer a dependency but 8 other projects are. No more mono-repo and goodbye to all the reasons it was considered a good thing.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      The problem with doing it all under one project is that it leads to labor sprawl and duplicate efforts. I support Ladybird but I think trying to recreate every single existing project is silly from a technical perspective. From a educational perspective it can be very useful.