‹ BackHN Continuity

Thread

Android 17 is the first since 3.x to add new APIs without releasing to the AOSP

1180 points · 723 comments · theanonymousone

  1. wps · · focus · HN ↗
    The amount of roadblocks Google is putting up for GrapheneOS is just ridiculous. None of their decisions make any sense, from the delayed source patches upstream, to the embargos, attestation issues, etc. Google simply regrets android being open source.
    1. godelski · · focus · HN ↗
      I hope people remember this when advocating for chromium. Just because it is open source doesn't mean they don't control it. We need to start the long process of hard forking now or turn to alternatives like Firefox as a new foundation.

        > Google simply regrets android being open source.
      Android wouldn't be what it is if it wasn't open source. With all the work from outside Google. The same is true chrome.

      But they won't learn that on their own. They are breaking the deals. So we move. We force their hand

      1. StilesCrisis · · focus · HN ↗
        Hard forking doesn't solve the problem of closed source.

        If the goal of a hard fork is "the community will invest equal resources that Google does today" then you wildly underestimate how many engineers work on Chrome.

        1. floxy · · focus · HN ↗
          >wildly underestimate how many engineers work on Chrome.

          It is completely insane how many people work on Chrome. It seems like it is time to deprecate web browsers and do something different. Like you get a frame-buffer to draw on with something like a wasm vm. Web pages get replaced by programs (which they essentially are anyway). Get rid of 99.9% of the cruft that has accumulated over the decades in browsers. If you want to have some of that cruft, that is a library you have to send.

          1. AnthonyMouse · · focus · HN ↗
            > Like you get a frame-buffer to draw on with something like a wasm vm. Web pages get replaced by programs (which they essentially are anyway).

            The biggest thing standing in the way of this is actually Apple, since they don't allow competing browser engines or equivalent so you can't make something like this for iOS whatsoever.

            1. floxy · · focus · HN ↗
              Apple can create a clone for their wall-garden.
              1. NetMageSCW · · focus · HN ↗
                Those times will never happen.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.