4 ms·

> The idea of my OS being run like this? Absurd. Isn't Android run like this? Is the community participation in Fuchsia different from that of Android i.e. Bui

> The idea of my OS being run like this? Absurd. Isn't Android run like this? Is the community participation in Fuchsia different from that of Android i.e. Build inside Google and publish the code to AOSP? Regardless of how 'open-source' android is, I'm grateful for its 'openness'. Cannot imagine mobile compute held solely by walled-gardens and carriers. Anyways Brian Swetland is the person to thank for those who appreciate the openness of android[1]. > “Peter mentioned something about exclusivity for our first device, which Brian overheard. By the time we got back to our hotel room, Swetland had threatened to resign because ‘I didn’t join Android to become another Danger.’ I was concerned because Brian was so critical to our success, but when I saw him the next day everything was fine.” > He was strongly in favor of Android’s vision for an open and independent platform. He threatened to resign several times during his time on the Android team over decisions that would have resulted in a closed platform. [1] https://arstechnica.com/information-technology/2021/08/excerpt-the-history-of-android-as-written-by-a-longtime-android-developer/ https://arstechnica.com/information-technology/2021/08/excer...

yakak 5y ago
Not so fast, in areas where the bug can be phrased as basic compatibility with a recognized standard it is often easier to get Google (or Apple, or ..) to flinch than areas with a mixed standard/implementation they think they own.
- Abishek_Muthian 5y ago
  > Not so fast, in areas where the bug can be phrased as basic compatibility with a recognized standard it is often easier to get Google (or Apple, or ..) to flinch Unfortunately, Like the parent I've been following couple of bugs for years which Google didn't 'flinch' yet; 'Chromium on Linux not respecting prefers-color-scheme when dark GTK theme is set'[1] is one such bug. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=998903#c83 https://bugs.chromium.org/p/chromium/issues/detail?id=998903...
  - yakak 5y ago
    It looks to me like they tried to flinch or at least didn't close it like almost everything UX I've seen on the chromium bug site. Pretty impressive given that while gnome is external its not an actual standard of the sort the Posix or RFC networking gangs kick each other in the crotch over. If they aren't publishing formal standards to an outside body that starts picking up independent interested parties, I think they will have more options to go down from their current quality whether or not the current quality is acceptable to critics today.

yakak 5y ago

Not so fast, in areas where the bug can be phrased as basic compatibility with a recognized standard it is often easier to get Google (or Apple, or ..) to flinch than areas with a mixed standard/implementation they think they own.

Abishek_Muthian 5y ago
> Not so fast, in areas where the bug can be phrased as basic compatibility with a recognized standard it is often easier to get Google (or Apple, or ..) to flinch Unfortunately, Like the parent I've been following couple of bugs for years which Google didn't 'flinch' yet; 'Chromium on Linux not respecting prefers-color-scheme when dark GTK theme is set'[1] is one such bug. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=998903#c83 https://bugs.chromium.org/p/chromium/issues/detail?id=998903...
- yakak 5y ago
  It looks to me like they tried to flinch or at least didn't close it like almost everything UX I've seen on the chromium bug site. Pretty impressive given that while gnome is external its not an actual standard of the sort the Posix or RFC networking gangs kick each other in the crotch over. If they aren't publishing formal standards to an outside body that starts picking up independent interested parties, I think they will have more options to go down from their current quality whether or not the current quality is acceptable to critics today.