3 ms·

It is unrelated technology. First version of Android runtime for chrome was ARC welder , if I remember correctly. But that didn't go anywhere. Right now they ar

by 0xFFC 10y ago

It is unrelated technology. First version of Android runtime for chrome was ARC welder , if I remember correctly. But that didn't go anywhere. Right now they are using something similar to docker technology which runs Android apps in sandbox in chrome. You can watch the talk in Google io 2016. So in this scenario there not feasible way to port this runtime to other platforms because it is not using chrome runtime.unless they redesign it.

tmzt 10y ago
My understanding of how this works, mostly from reading commit messages and poking around the repo, is to add a wayland compositor/server to the aura component of chromium. Aura is the window manager, compositor, and render of ui items such as the task bar and status icons of ChromeOS. It looks like the Android portion is largely based on the same fork as ARC, with the rendering performed through Wayland. It also looks like a large number of Android APIs had to be reimplemented which may excacerbate the fragmentation problem.
- 0xFFC 10y ago
  Cool , did they used Wayland? I didn't know that. It is quite fascinating, Wayland finds its actual place in industry. About API reimplantation, I do remember a little bit, you are correct, the guy in Google talk mentioned it is simultaneous development to Android and they are not using Android underlying technology on top of namespace,etc (Linux syscalls). I would love to read a blog post about this, and since your poked around in source code you are right person. So please, if you have any spare time, write a blog post.
oDot 10y ago
A Linux port is actually feasible: > the Android container itself has no plans to be released (which is basically just the rootfs of an Android system). everything else is already released, and as noted, is using standard Linux technology to isolate things (namespaces, etc...). > with that in mind, there's nothing stopping people from implementing this approach elsewhere. https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-discuss/OfBln-hl7ug https://groups.google.com/a/chromium.org/forum/#!topic/chrom...
- 0xFFC 10y ago
  Yeah of course , but we are talking about chrome as browser. I would love to see semiofficial Android runtime for Linux.
asimuvPR 10y ago
I was part of the ARC program as a publisher and it was financially successful for my team. I can't praise Google enough for it. The tech worked well although I don't oppose their new approach. The seem to have learned a lot from ARC and decided to move forward.

by 0xFFC 10y ago

tmzt 10y ago

My understanding of how this works, mostly from reading commit messages and poking around the repo, is to add a wayland compositor/server to the aura component of chromium. Aura is the window manager, compositor, and render of ui items such as the task bar and status icons of ChromeOS. It looks like the Android portion is largely based on the same fork as ARC, with the rendering performed through Wayland. It also looks like a large number of Android APIs had to be reimplemented which may excacerbate the fragmentation problem.

0xFFC 10y ago
Cool , did they used Wayland? I didn't know that. It is quite fascinating, Wayland finds its actual place in industry. About API reimplantation, I do remember a little bit, you are correct, the guy in Google talk mentioned it is simultaneous development to Android and they are not using Android underlying technology on top of namespace,etc (Linux syscalls). I would love to read a blog post about this, and since your poked around in source code you are right person. So please, if you have any spare time, write a blog post.

oDot 10y ago

A Linux port is actually feasible: > the Android container itself has no plans to be released (which is basically just the rootfs of an Android system). everything else is already released, and as noted, is using standard Linux technology to isolate things (namespaces, etc...). > with that in mind, there's nothing stopping people from implementing this approach elsewhere. https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-discuss/OfBln-hl7ug https://groups.google.com/a/chromium.org/forum/#!topic/chrom...

0xFFC 10y ago
Yeah of course , but we are talking about chrome as browser. I would love to see semiofficial Android runtime for Linux.

asimuvPR 10y ago

I was part of the ARC program as a publisher and it was financially successful for my team. I can't praise Google enough for it. The tech worked well although I don't oppose their new approach. The seem to have learned a lot from ARC and decided to move forward.