4 ms·

Most apps ship with multiple binaries for the appropriate architecture. For those apps that don't have the necessary binaries the native code will be translated

Most apps ship with multiple binaries for the appropriate architecture. For those apps that don't have the necessary binaries the native code will be translated on the fly to the host architecture instruction set. Since Chromebook's are significantly faster than smartphones the small performance hit shouldn't be noticeable.

sounds 10y ago
There are also many Arm Chromebooks.
- Grazester 10y ago
  Are there?
  - 0x6c6f6c 10y ago
    They are pretty well split. Many x86 Chromebooks offer several tiers that obfuscate the data, but in terms of product line releases, they're about 50/50. Both Samsung Chromebooks, ASUS Chromebook Flip, HP Chromebook 14 G3, Haier and Hisense's both as well, for example, are ARM devices.
  - Grazester 10y ago
    Ah, the list of x-86 Chromebooks easily out number the ARM ones available.
thescriptkiddie 10y ago
Source? On Android and under ARC you're SOL if an NDK app doesn't provide binaries for your architecture. This is rarely an issue though, as most apps just opt to ship with binaries compiled for every supported ABI. https://developer.android.com/ndk/guides/abis.html https://developer.android.com/ndk/guides/abis.html
- izacus 10y ago
  That's not really true - x86 devices mostly come with libhoudini layer which can load and translate ARMv7 binaries on the fly. Hence if the app ships armeabi code you're pretty much set.
- bitmapbrother 10y ago
  ARC is dead. The Android Framework in ChromeOS is now a container.
twotavol 10y ago
"For those apps that don't have the necessary binaries the native code will be translated on the fly to the host architecture instruction set" How would this happen?
- masklinn 10y ago
  Via an ARM/Android emulator? There's already one in the android development suite.
  - fla 10y ago
    Thanks god no :) That would be really slow and painful. It is a translation layer, not an emulator.
  - bitmapbrother 10y ago
    binary translation.

sounds 10y ago

There are also many Arm Chromebooks.

Grazester 10y ago
Are there?
- 0x6c6f6c 10y ago
  They are pretty well split. Many x86 Chromebooks offer several tiers that obfuscate the data, but in terms of product line releases, they're about 50/50. Both Samsung Chromebooks, ASUS Chromebook Flip, HP Chromebook 14 G3, Haier and Hisense's both as well, for example, are ARM devices.
- Grazester 10y ago
  Ah, the list of x-86 Chromebooks easily out number the ARM ones available.

thescriptkiddie 10y ago

Source? On Android and under ARC you're SOL if an NDK app doesn't provide binaries for your architecture. This is rarely an issue though, as most apps just opt to ship with binaries compiled for every supported ABI. https://developer.android.com/ndk/guides/abis.html https://developer.android.com/ndk/guides/abis.html

izacus 10y ago
That's not really true - x86 devices mostly come with libhoudini layer which can load and translate ARMv7 binaries on the fly. Hence if the app ships armeabi code you're pretty much set.
bitmapbrother 10y ago
ARC is dead. The Android Framework in ChromeOS is now a container.

twotavol 10y ago

"For those apps that don't have the necessary binaries the native code will be translated on the fly to the host architecture instruction set" How would this happen?

masklinn 10y ago
Via an ARM/Android emulator? There's already one in the android development suite.
- fla 10y ago
  Thanks god no :) That would be really slow and painful. It is a translation layer, not an emulator.
- bitmapbrother 10y ago
  binary translation.