• kadu@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        1 year ago

        Do you use Android? Chrome is the native WebView that a good chunk of your apps use. Without deep modifications, you can’t use another webview. Do you use iOS? Safari not only renders any HTML component on any app, it’s also the engine behind every single browser on the OS - Chrome on iOS is Safari with different clothing. Do you use an Xbox? A PlayStation? I could go on.

        While Linux does indeed handle this differently, with most apps bundling their own web rendering engine, Windows and many other systems use one main core browser that other apps call when they need web pages. This is got many advantages and many disavantages. If you dislike it, fair enough - but let’s not pretend this is unusual or somehow unjustifiable.

        • somedaysoon@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 year ago

          Do you use Android? Chrome is the native WebView that a good chunk of your apps use.

          Wait… so you are talking about webviews when I was talking about the actual browser? Lmao… talk about a false equivalency.

          This is got many advantages and many disavantages. If you dislike it, fair enough - but let’s not pretend this is unusual or somehow unjustifiable.

          I’m talking about forcing the actual browser installation. Nothing you said has countered this, Android doesn’t force Chrome to be installed for webviews in applications. The webview class is nothing close to being a full browser, and certainly doesn’t require a browser to be installed to use it. If anything, that is an example of the right way to do it… having a separate class, that is not dependent on the actual browser installation.

          Yes, please go on, I can’t wait to hear more of your ridiculous takes.

    • ultranaut@lemmy.world
      link
      fedilink
      arrow-up
      5
      arrow-down
      2
      ·
      1 year ago

      There’s a “Getting Started” app built in to win11 that is both completely useless and totally unremovable by any method without breaking the OS.

      • kadu@lemmy.world
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        1 year ago

        That’s because it’s not an app. Do “Winget list” and you’ll see it’s not there.

        It’s part of the shell. Open it up, look at task manager, and you’ll see it’s not spawning new processes. Which also mean it’s irrelevant - it doesn’t add any background tasks, modifies any files or in anyway interfere with the users. It’s quite literally just an icon created by the shell.

    • Sanctus@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Its more of the dependency chain. I wouldn’t consider tying your taskbar, web browser, and other microservices together like that a good thing in any ecosystem. Its not really the fact that removing system files breaks your system. Its that the taskbar and web browser should not be considered Core. People want to choose and not have their non-choice staring at them with their new gurl from the sidelines.