Hacker News Reader

Comment by tyingq | Hacker News Reader

Are there enough clues to figure out if this is intended to eventually displace Android, ChromeOS, the Ubuntu distribution most googlers use on their company machines, or the Linux they run their data centers?

As far as I know, Google hasn't telegraphed the purpose of it. I can't tell if it's targeted at all, none, or some of the above.

View on HN

More likely this exists simply because Google could afford it. If something comes out of it, fine; if not no problem. When money is no object why not let some engineers play with experimental tech.

Your guess is as good as mine, but there are some clues:

https://techspecs.blog/blog/2017/2/14/googles-not-so-secret-...

https://techspecs.blog/blog/2017/2/15/proof

Thanks, but would sooner recommend my third article: https://techspecs.blog/blog/2017/3/15/fuchsias-hypervisor.

The link in the bottom of your first article was very helpful, and seems to confirm ChromeOS and Android would be the likely targets.

https://fuchsia.googlesource.com/magenta/+show/master/docs/m...

Thanks. Yeah, they really could not be more transparent about that. Most of the bring-up is on mobile + PC silicon as well.

There's no need to kill Chrome OS for the education, mind.

Looked at it again, and it could be an old comment about magenta, and maybe not applicable to fuchsia?

Well, the OS is most strictly the kernel, right? It's honestly all together. It's an SMP system that you can already run on normal ARM and x86 devices.

The team has stated that everything in the kernel is true, and that there's quite a lot there to infer from. What they can't say publicly is the how and why, e.g. how would they hypothetically implement backwards compatibility with Android apps?

Reply on news.ycombinator.com