[crapple8430]

I do think that Android is bad-faith open source too, but not in that sense. It's bad faith open source because only AOSP is actually open source, and AOSP by itself is not that useful of an operating system. There are a lot of proprietary components required for a functioning Android phone, usually known as Google apps, which are not open source. Android as a system is better described as open core, not open source. There are even mechanisms to prevent you from using your own fork, such as the various "integrity" APIs.

[DannyBee]

" It's bad faith open source because only AOSP is actually open source, and AOSP by itself is not that useful of an operating system. "

So it's bad faith because they didn't open source as much as you wanted, and you want parts that aren't open source because you don't find it useful enough.

Have you considered that maybe this is not a great bar?

Your claim of bad faith is based on what you want, and not based on how any of the people involved actually operated.

Perhaps you should not claim bad faith without evidence the people involved actually operated in bad faith.

Thankless people for whom somebody's particular open source project is not enough and feel like they are entitled to more are one of the worst things about open source as an ecosystem overall.

On top of that, i'm very curious to understand what exactly you think would be the state of the world had AOSP not been released.

(Also, as an aside, open core did not exist at the time AOSP was released)

[SuperNinKenDo]

I mean, parent does point out that we have another term that's probably less misleading (open-core), and there does have to be _some_ point at which a project can no longer call itself Open-Source and be taken seriously or in good faith. If a project Open-Sources one 20-line header file in a 6M LOC project, calling it Open-Source would be a straight up lie.

I think something like "Is it actually reasonably possible to build something usable from the parts that are Open-Source?" Is not a bad line in the sand, though it's not a very clean one.

You can quibble about it generally, or talk about case-by-case specifics, but your outrage seems a bit out of proportion, it's a reasonable position to take.

[DannyBee]

Here, they open sourced an entire buildable phone OS that you could build and flash on a phone and have it work.

At a time when none really existed. Not even close.

They also went out of their way to generate open drivers and rewrite those where vendors would not give them some, and ensure they had contracts that let them do so.

Calling this open core is also insane even if it wasn't a retcon. At the time, >95% of all android code in existence was open source. Probably closer to 99%. The remaining pieces were mostly related to prototype phones that never saw the light of day.

How is it possibly "less misleading" to call this release "open core"?

How it is a reasonable position to literally accuse them of bad faith because the parent didn't think it "useful enough"?

Admittedly I think open core is just a definition someone made up to beat others over the head with for "not being open source enough", so I wouldn't use it anyway[1].

But here, moving the goal posts because it didn't include whatever particular piece the parent wants does not make it a reasonable position, and it definitely is not a reasonable one. Nor is the completely unsubstantiated bad faith accusation.

My outrage is because i tire of watching people tear down things and literally accuse folks of bad faith because, 20 years later, they decided it wasn't good enough for them. The fact that this doesn't outrage more people says a lot more about how the open source community behaves than it does about android.

If this is the bar for reasonable positions, it's a really crappy bar.

[1] FWIW - while i was not always, i'm fairly consistent these days in believing that all the forms of trying to shit on open source releases or come up with no-true-scotsman terms to use for not being "something" enough are a plague, regardless of whether that something "accepting features that i want" or "releasing pieces that i want" or whatever. The sense of entitlement involved is often impressive. Was it released under an open source license? Cool it's open source. Period. I'll just be thankful someone took the time to share and use what ever they did share to build cool things. They don't owe me crap.

[ChadNauseam]

The integrity APIs are horrible. Why can you not send RCS messages from a rooted phone or use the ChatGPT app?

[charcircuit]

>and AOSP by itself is not that useful of an operating system

Why not? What useful feature is gated behind a proprietary API. Casting is one I can think of. But I think you can still get plenty of use out of a phone without casting.

There is technically a casting API in AOSP but it's old and doesn't integrate with Chromecast as well.