‹ 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. seb1204 · · focus · HN ↗
          Not denying than many engineers work on Chrome just wondering how many of them work on Chrome features that are anti pattern, reducing privacy, improving information collection or tracking or against users interest in broad.
          1. StilesCrisis · · focus · HN ↗
            You can just look at the commit stream and see for yourself. Despite community pearl-clutching, 99% of the work is just good old fashioned software engineering.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.