• vzqq@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      5
      ·
      6 hours ago

      Is it? Once you have committed to showing “content from around the web” you are locked into spawning a web view. Then you might just as well use js for the web view bits.

      The real issue is embedding a browser on the start menu to shove stupid drivel at your eyeballs. Using js to do it seems like a decent engineering practice.

      • Cethin@lemmy.zip
        link
        fedilink
        English
        arrow-up
        7
        ·
        5 hours ago

        No you aren’t. There are a million ways you could handle this that don’t require a web view. Saying that means anything that retrieves any information from a server needs one. All it needs to do is retrieve the information that needs to be displayed from a server. I don’t know what all they serve through it, but it could easily provide the text and images needed without a web view.

        • vzqq@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          You misunderstand.

          Displaying web content is a business requirement, not a technical one. Everything follows from there.

          Besides, they need full JavaScript to allow the partners to inject tracking code to make sure they are getting to what they paid for. You. The product.

          • Cethin@lemmy.zip
            link
            fedilink
            English
            arrow-up
            6
            ·
            5 hours ago

            Well sure. If the requirements are stupid then they’re stupid. That’s not what you said before though. Showing content from the web doesn’t create stupid requirements.

            • vzqq@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              2
              ·
              4 hours ago

              I said “content from around the web”, in quotes. It’s what Microsoft calls this feature, that originated in Edge collections and spread like a plague over a bunch of UI elements.

              It’s ok if you don’t know things. You don’t have to be a jackass about it.

              • Cethin@lemmy.zip
                link
                fedilink
                English
                arrow-up
                4
                ·
                3 hours ago

                I upvoted your reply until I got to your last sentence. I haven’t been rude. Why are you being rude? Meanwhile telling me not to be a jackass about it…

    • Sanctus@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      26
      ·
      14 hours ago

      Yes, a hodgepodge of shit is of course worse. But fucken say that then. Dont say, “its literally a react native application! Thats why its so bad!” when that is not true and sounds ignorant.

      • Septimaeus@infosec.pub
        link
        fedilink
        English
        arrow-up
        7
        ·
        11 hours ago

        Personally, I am 100% grateful for this correction, because I didn’t know and since I’ve heard the less accurate ragebait version dozens of times at this point I would have been confused, next time I have to spin up a Win11 image, why I couldn’t replicate the spike I’ve heard so much about. The fact that it’s tied to a particular UI component, one of many that machine provisioning scripts and playbooks commonly disable, means it would have remained a bothersome unresolved mystery to me forever if not for your comment. So thanks.

        • Sanctus@anarchist.nexus
          link
          fedilink
          English
          arrow-up
          7
          ·
          10 hours ago

          Oh it still spikes without the recommendations lmao at least my work laptop was because I, too, have all the bullshit registry entries to make Start Menu usable and resource monitor was showing 10% spikes on average each time I opened the start menu. Wild.