zlacker

>>logic_+(OP)
Welcome to ChromeOS 2.0

>>refulg+j2
I suspect there is going to be an amalgamation between ChromeOS, Android and Fuchsia.

There is heavy work underway in fuchsia currently to provide Linux kernel comparability via a subsystem they call starnix.

They are already I believe looking at running a version of fuchsia in a vm on Android.

Then there was also a lot of talk about the androidification of ChromeOS.

It sure looks like we are moving towards some kind of cross device OS that is distinctly Google’s without Linux in the future.

>>mdhb+Z3
What’s the point of running fuschia on android? It should be the other way around: android vm on fuschia.

>>nashas+E6
Fuchsia as the core makes much more sense. It replaces Linux for a start and completely changes the security model to something a LOT more defendable among a bunch of other benefits.

>>mdhb+39
I worked on Android at Google until 2023 and can 99.999% confirm for you Fuchsia, as the outside understands it is DOA. (i.e. as some sort of next gen OS, and if not that, some kernel that's on track to replace Linux in Android)

Long story short is you can imagine in 2019 there was X amount of engineers, 95% on Android and 5% on what you'd call Fuchsia.

The central argument up top became about why the renegade band that split off from Android/Chrome etc. to do Fuchsia in...early to mid 2010s?...and if it was going to provide a significant step forward. This became framed in terms of "$ of devices shipped", in which case, there was no contest.

Funnily enough this very article is about N dominos down from there (de-investment in Fuchsia, defenestration of head software guy of Android/Chrome/Chrome OS etc., ex. Moto hardware guy is in charge now)

Don't read this comment too closely, I was not in the room. For example, I have absolutely no actual quotes, or relayed quotes, to 100% confirm some set of individuals became focused on # of devices shipped.

Just obsessive enough to track wtf was going on, and on big enough projects, and trustworthy and hard working, and clearly without party or clique, such that I could get good info when asked, as it was clear my only concern was making things that were good and making sure all of Google's products could be part of that story.

>>refulg+tN
Thanks for that insight. Obviously there’s a lot of context in there that isn’t at all clear outside.

One part I find hard to reconcile with all of that is that even just looking at public facing stuff alone it seems to be under VERY active development.

I count 100 commits in just the past 24 hrs here: https://fuchsia.googlesource.com/fuchsia/+log and it’s been at that pace for a LONG time.

Which leads me to ask… what is up with it in your opinion because that’s hard to match up with DOA

Also I wasn’t making up the idea that they were in the process of bringing in this “microfuchsia” VM into Android although it’s purpose is unclear.

>>mdhb+TZ
You're seeing the public facing side of it as a wholesale Android replacement, think of this repo as the tip of the iceberg: well, it used to be, but the rest of the iceberg disappeared.

It's still shipping, successfully, on millions(?) of devices yearly via Nest Hubs and such. Never say never. But all public-facing signs are fairly clear, the big move is ChromeOS into Android, not Android onto Fuchsia - and note how invested Google is in the Nest Hubs (read: not at all, languished for years now)

(I'm also curious if we could get a stats-based thing on, say, 2019 vs. 2024, My out-of-thin-air prior would be 30% more activity in 2019 than now. But I also figured there was 10 commits a day now, not 100.)

(I tried checking out the whole repo, but then all the apps on my macbook informed me en masse there was 0 disk space left :X Doesn't look like there's a GitHub mirror)

(cheers btw, you're my kind of people, one of the more soul-sucking parts of Google was finding out that kind of person is few, and far between) (i.e. curious and into It, not just here to make your boss or partner happy)