• nossaquesapao
    link
    fedilink
    arrow-up
    86
    ·
    3 months ago

    And here we have a clear example of how Chrome’s almost monopoly is a bad thing for us.

    • ℍ𝕂-𝟞𝟝@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      60
      ·
      edit-2
      3 months ago

      Not almost monopoly.

      Google is a monopolist, and it has acted as one to maintain its monopoly,

      - the US govt

    • Steve@communick.news
      link
      fedilink
      English
      arrow-up
      26
      ·
      3 months ago

      Monopolies don’t require 100% of a market. Just enough to effectively manipulate a market.

      One firm might only be 10% of a market. But if every other firm is only 1-2%, that 10% will have an outsized monopolistic ability to manipulate that market.

    • Norah - She/They@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      8
      ·
      3 months ago

      AV1 Image File Format is an open, royalty-free image file format

      While I am by no means trying to defend Google, or their monopoly, I’m struggling to see how this time is a “clear example” of monopolistic behaviour?

      Like, take for contrast the Moving Picture Experts Group (MPEG) image format HEIC, which Apple has adopted as it’s main high-res format on iOS. It’s proprietary, and that fact is indeed worrying. However, the only reason I can figure out for Google’s move here being a ‘bad’ thing, is if you’re nostalgic about the .jpg extension…

      • nossaquesapao
        link
        fedilink
        arrow-up
        14
        ·
        3 months ago

        I didn’t mean the choice of image format is a monopolistic behavior, but that the monopoly puts google in a position that any choice they make, be it a good or bad one, becomes an industry standard, without others having any choice in it.

      • Markaos@lemmy.one
        link
        fedilink
        arrow-up
        3
        ·
        3 months ago

        Why not just say Rust? There isn’t really anything else that would provide good enough performance for a browser engine with modern heavy webpages while also fixing some major pain point of C/C++

          • Markaos@lemmy.one
            link
            fedilink
            arrow-up
            1
            ·
            3 months ago

            Zig didn’t come to my mind when I was writing my comment and I agree that it’s probably a decent option (the only issue I can think of is its somewhat small community, but that’s not a technical issue with the language).

            My argument against Go and Java is garbage collection - even if Java’s infamous GC pause can apparently be worked around with a specialized JVM, I’m pretty sure it still comes at the cost of higher memory usage and wasted CPU cycles compared to some kind of reference counting or Rust’s ownership mechanism (not sure about the proper term for that). And higher memory usage is definitely not something I want to see in my browser, they’re hungry enough as is.