Android 17 is the first since 3.x to add new APIs without releasing to the AOSP
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Android 17 is the first since 3.x to add new APIs without releasing to the AOSP
Unofficial Hacker News client; not affiliated with Y Combinator.
wps · · focus · HN ↗
godelski · · focus · HN ↗
But they won't learn that on their own. They are breaking the deals. So we move. We force their hand
StilesCrisis · · focus · HN ↗
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.
ocdtrekkie · · focus · HN ↗
Playing at their table is a losing game, the house always wins.
charcircuit · · focus · HN ↗
The reason why no one runs AOSP is because the phone market rewards differentiation. Each phone manufacture wants to build their own experience and building on top of AOSP is how they do so.
Is it really a losing game? Building a new OS from scratch is not worth it. Why throw away an entire app catalog for your device? Consumers want access to existing app catalogs when buying a phone. If anything is a losing game it's building a new mobile operating system over forking Android as a base.
swiftcoder · · focus · HN ↗
Assuming you can get a hardware vendor to support your fork.
Android has always been a weird blend of proprietary BSPs wedged together with the core AOSP project - we used to have an entire team whose full-time job was merging the Qualcomm BSP into our AOSP fork. At the time you didn't even get access to that BSP without inking a deal with QCOM...