• el_abuelo@lemmy.ml
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    6
    ·
    4 months ago

    It’s easy to understand when you think most comments are similar to yours and don’t provide any insight as to why this might be a problem.

    Maybe you could update your post and share your knowledge and experience with others, so that there are less people in the world who don’t see the problem.

    • rdri@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      4 months ago

      When trying to render a relatively simple page consisting few thousands of text lines in a table, any current browser will cause mouse cursor to lag for some time, then you’ll discover it consumes at least 2 GB ~ 4 GB of RAM. YouTube lags like I have 2 cores instead of 16. Any electron app is either clunky or too clunky, also either hungry or too hungry.

      I’m sorry but I don’t have time to look up other cases.

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months ago

        Any intuition on why we’d expect opening the same page on a newly implemented browser engine that implements all equivalent standards and functions will consume less resources?

        • rdri@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 months ago

          That’s not an expectation. The experience is that this became a reality thanks to google, and that it will only get worse in the future. More competition within browsers is the expectation. Better chance for better frameworks to emerge. Eventually it may cause google code to shift into a better overall state too.