• cm0002@lemmy.world
      link
      fedilink
      arrow-up
      22
      ·
      1 day ago

      We need a more diverse browser engine market to keep the web open.

      We definitely do, but it’s a tall order considering making a fully functional and daily usable browser engine is one of the most difficult programming projects to under take

      At least we got Ladybird with its brand new from scratch engine coming up though! (In 2028…)

      • bettertecheu@lemmy.world
        link
        fedilink
        arrow-up
        23
        ·
        1 day ago

        It’s absolutely not a simple thing, but if we let the web turn into Chrome-only then Ladybird doesn’t stand a chance. For now, more market share for Firefox and Firefox-based browsers is the only argument against making websites only work in Chrome.

        • taladar@sh.itjust.works
          link
          fedilink
          arrow-up
          5
          ·
          1 day ago

          Especially if Chrome is bought by OpenAI or some of the other players who want to enshittify it even faster and have shown interest.

      • univers3man@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        3
        ·
        1 day ago

        I can’t get behind a browser built from scratch with C, not Rust, considering how integral browsers are to security these days. Plus there’s the whole controversy around their pronouns and politics in coding stances.

        • realconor@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          what’s wrong with C? if it’s causing issues that it’s written in C, it’s the developers whom are being entrusted with projects that are out of their depth in a project they shouldn’t be responsible for at fault rather than the time-tested language

          • univers3man@lemmy.world
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            4 hours ago

            It’s not that C is bad, but that it’s a bad language in this use case. Rust doesn’t let developers shoot themselves in the foot as easily as C, not to say that it can’t be done.

            The comment regarding developers being responsible is true, but they could make their job much easier and thus more accessible to others by using Rust and not being required to learn all the tricks to make C safer in such a critical piece of software.

            This isn’t a paid product/gig, so it’s not necessarily attracting top C developers either.

            C is great for specific user cases such as code that needs to be exceedingly performant, needs to access low-level devices, or is used on embedded applications.

            On a project that doesn’t have these requirements, I believe it is more important to be understandable and has a lower skill floor.