←back to thread

442 points logic_node | 6 comments | | HN request time: 0.206s | source | bottom
Show context
refulgentis ◴[] No.43973538[source]
Welcome to ChromeOS 2.0
replies(2): >>43973601 #>>43973642 #
bobajeff ◴[] No.43973601[source]
Yeah that's what immediately came to mind. This must be part of their effort to merge Chrome OS into Android. On the Chrome OS side they already said are going to be replacing the kennel and other system stuff with Androids guts.
replies(1): >>43973647 #
1. Miraste ◴[] No.43973647[source]
That's sad news. ChromeOS is much faster and more efficient than Android. Turning off the Android subsystem in low-end Chromebooks is a huge performance boost, even when no Android apps are open.
replies(2): >>43973743 #>>43976695 #
2. odo1242 ◴[] No.43973743[source]
To be fair, that’s likely because the Android subsystem is a virtual machine - not running multiple sets of system services / CPU emulation on a computer will make it faster pretty much universally.
replies(2): >>43973794 #>>43974786 #
3. nashashmi ◴[] No.43973794[source]
Yup, the android vm is too much for a chrome pc unless it’s a high end device.

I can’t imagine android going faster than chrome at a native level either.

4. Miraste ◴[] No.43974786[source]
It's not just the virtualization, ChromeOS has had a lot of work put into performance. The low-end ARM Chromebooks use the same hardware as budget Android devices, and they're noticeably faster. My Android phone uses more RAM doing nothing from a fresh boot than those Chromebooks even have.
replies(1): >>43981528 #
5. refulgentis ◴[] No.43976695[source]
Breaks my heart (worked on Android from 2016-2023, ChromeOS was a revelation. Alas, Efficiency™. (as in salaries, not the things we build))
6. odo1242 ◴[] No.43981528{3}[source]
That’s a good point actually. Windowed app performance on Android apps is especially bad since they’re not designed for it (most of my experience is on Android-x86, but window resizing performance is not great)