Better is ChromeOS 67 enables running your own containers without having to put CB in developer. It uses the KVM to run a second Linux kernel. So you will be able to use GNU/Linux applications including Steam. More to be shared at Google IO this year.
Android container in Chrome OS
91–100 of 140 posts
Re: Android container in Chrome OS
#92Earlier quoted context omitted.
Apple systems are great precisely because they’re single platform and closed-source. It would be unfortunate if that changed.
I don’t see how you arrived at that conclusion. Why is the software not being open source a benefit?
Some people prefer open platforms that they can customize and tinker with. Some people prefer closed platforms where the defaults are good enough and you never have to open the hood. Neither of those preferences are more wrong than the other one. It's just a preference.
Re: Android container in Chrome OS
#93Earlier quoted context omitted.
I don’t see how you arrived at that conclusion. Why is the software not being open source a benefit?
Some people have different tastes. I know a lot of people who drive a Honda because it's easy for them to repair on their own, and parts are cheap. I know others who drive a BMW even though it's difficult and expensive to repair, because they would never repair it themselves so it doesn't matter. They value the experience of driving "the ultimate driving machine" even if it costs more and is harder to repair. Some pe…
Re: Android container in Chrome OS
#94Earlier quoted context omitted.
I don’t see how you arrived at that conclusion. Why is the software not being open source a benefit?
Some people have different tastes. I know a lot of people who drive a Honda because it's easy for them to repair on their own, and parts are cheap. I know others who drive a BMW even though it's difficult and expensive to repair, because they would never repair it themselves so it doesn't matter. They value the experience of driving "the ultimate driving machine" even if it costs more and is harder to repair. Some pe…
Re: Android container in Chrome OS
#95I can't wait for the day that phone operating systems development environments are a docker pull away. It's encouraging to see Google approaching my ideal workflow using containerisation. Apple systems are great until you run into the garden walls and are forced to use closed-source single platform software like Xcode. Chrome OS and Android are a lot more open in many respects. Hopefully efforts like this continue wi…
To be fair you can't go very far without running into garden walls in Apple land. It doesn't just apply to development. Want to change your launcher / dialer / etc? WALL! Want to run a different web browser (an ACTUAL web browser complete with JS / CSS engine). WALL! Want emulators or adult-themed apps? WALL! Want to develop for iOS or macOS on Windows or Linux? WALL! The list goes on and on...
Re: Android container in Chrome OS
#96Better is ChromeOS 67 enables running your own containers without having to put CB in developer. It uses the KVM to run a second Linux kernel. So you will be able to use GNU/Linux applications including Steam. More to be shared at Google IO this year.
Are you sharing a rumor/insider knowledge? Can I do this right now?
From crosh:
vmc start dev start_container.sh --container_name stretch --user --shell
That should drop you into a shell in a debian stretch distro. You can install packages and launch them. I haven't figured out if there's a way to pin them to the shelf yet and launch that way.
Re: Android container in Chrome OS
#97Earlier quoted context omitted.
To be fair you can't go very far without running into garden walls in Apple land. It doesn't just apply to development. Want to change your launcher / dialer / etc? WALL! Want to run a different web browser (an ACTUAL web browser complete with JS / CSS engine). WALL! Want emulators or adult-themed apps? WALL! Want to develop for iOS or macOS on Windows or Linux? WALL! The list goes on and on...
ChromeOS is significantly more locked down than macOS, developer mode notwithstanding. Firefox for iOS may use WebKit, but Firefox for ChromeOS isn't even a thing.
Re: Android container in Chrome OS
#98Earlier quoted context omitted.
To be fair you can't go very far without running into garden walls in Apple land. It doesn't just apply to development. Want to change your launcher / dialer / etc? WALL! Want to run a different web browser (an ACTUAL web browser complete with JS / CSS engine). WALL! Want emulators or adult-themed apps? WALL! Want to develop for iOS or macOS on Windows or Linux? WALL! The list goes on and on...
ChromeOS is significantly more locked down than macOS, developer mode notwithstanding. Firefox for iOS may use WebKit, but Firefox for ChromeOS isn't even a thing.
2. It's no longer true now you've got Android app support. Whether you think this is a good thing or a bad thing depends on your feelings about point 1.
3. "developer mode not withstanding" - well it is withstanding. You'd hear a lot less moaning about iOS if that had a similar mode.
Re: Android container in Chrome OS
#99Earlier quoted context omitted.
You know, there once was a time when we did everything in folders and didn't need the overhead of containerization just to keep well behaved things from stepping all over each other and breaking everything. Like all progress in computing we've reinvented the wheel, but now with a few additional layers of abstraction and the consequential performance degradation.
> You know, there once was a time when we did everything in folders and didn't need the overhead of containerization just to keep well behaved things from stepping all over each other and breaking everything. Those were the days…when we didn't have stupid watchdogs like memory protection and preemptive scheduling, and we all shared resources nicely and fairly, all the time. There were never crashes because someone to…
Re: Android container in Chrome OS
#100I just had a vision of all major OS projects providing developer containers for their projects. Like, you could just pull the latest Firefox dev container and run a single command to have a running debuggable app. I know one of the major pains we have when on-boarding new people is the whole dance to get to that first working build / first meaningful change. I can imagine this being significantly more simple if a wor…
Exactly what Google has done with ChromeOS 67. You can run GNU/Linux applications as containers. But extra safe as a container on a separate kernel through a VM using KVM. Versus they did Android as a container on the same Linux kernel as ChromeOS. But locked to only an Android container.
Do you need to run gnu/linux apps inside containers or can they just run inside the VM running on top of chromeos?