3 ms·
Does this mean that multi-threaded Chromebook applications go away? Android doesn't really do threads in the usual sense. It mostly uses a hack involving multip
by Animats 2y ago
Does this mean that multi-threaded Chromebook applications go away? Android doesn't really do threads in the usual sense. It mostly uses a hack involving multiple processes. And the "main thread" is very special.
- ignoramous 2y agoAndroid has had multi-threading for as long as I can remember. In fact, Binder RPC, that runs in every app process, itself is multi-threaded. What's special in Android is multi-process. All (Kotlin/Java) apps fork from the same base runtime image, regions of which are CoW'd when mutated.
- roywashere 2y agoThis is not really moving ChromeOS to Android, but rather using their Android Bluetooth component over the crusty Linux blueZ-thingy. And they even talk about the possibility of running the Android Bluetooth component on normal Linux. So there would be no ‘threading’ like repercussions as far as I would see?
- veeti 2y agoHow do you mean? You can spin up threads using stock Java API or pthread on NDK. (If you intend to run them in the background your app will need an active foreground service to not get killed, though). As far as the "main thread", I don't think that's unusual for most user interface frameworks.