4 ms·
No surprises there. RISC-V is the future, and Google itself already has some public RISC-V designs. The expectation is that some Pixel in not so distant futur
by snvzz 4y ago
No surprises there.
RISC-V is the future, and Google itself already has some public RISC-V designs.
The expectation is that some Pixel in not so distant future will debut with a highly competitive RISC-V SoC.
- bitL 4y agoThey are designing a new chip for their cloud...
- booi 4y agoDidn’t they just release their ARM virtual servers?
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- viraptor 4y agoThat's going to be interesting to see. Apple could pull off the change in infrastructure and tell devs to deal with it. But could Google do the same with lots of apps in the store which contain native code?
- izacus 4y agoNot sure what you're talking about here, Android supports 4 architectures right now (supported 6 before) and adding one more isn't such a big deal.
- viraptor 4y agoI know android itself can support multiple archs, but does a (random play store app with native library) support them or even test them all?
- izacus 4y agoMost Play apps have no NDK code so they work fine.
- iggldiggl 4y agoNot claiming it's a representative sample, but my phone has 160 subfolders underneath /data/app (i.e. user-installed/-updated apps), of which after a quick count 52 include native libraries. I don't even have that many games on my phone, so those only account for six of those apps, with the largest fraction being various multimedia apps (camera, video player, image editor, music player, even my e-book reader…)
- kernal 4y agoThe top Play apps and games use native libraries. Here's a CppCon talk that mentions that 75% of the top 100 Play apps and games use C++. https://youtube.com/watch?v=2Y47g8xNE1o&feature=shares https://youtube.com/watch?v=2Y47g8xNE1o&feature=shares
- 0cf8612b2e1e 4y agoNot an Android developer, but it seems that all I hear is the upgrade treadmill for Android APIs. That is without changing the underlying architecture.
- marticode 4y agoWell the benefit of having Java/Kotlin being the default dev language for Android is there's no need to recompile to run those apps on another arch. Only apps with native code will be an issue.
- viraptor 4y agoWhere "only" means majority of games, especially anything created with common game frameworks, and non-trivial apps with native dependencies they pulled in.
- iggldiggl 4y ago"Multimedia" apps (anything image, video or audio-related, and even my e-book reader) are probably another large fraction (and since I don't have all that many separate game apps installed – mostly a few emulators only – they're actually the largest fraction of apps with native libraries on my phone).
- mkl 4y agoWhen Intel was trying to make x86 phones a thing they supplied Google with an ahead-of-time binary translation system. The same could be done with RISC-V.
- crossroadsguy 4y agoYup. They can and they can also tell the devs to deal with it. Android devs, like me, aren’t into android development for the love of the dev tools and the environment (which are pathetic at best). They are there because they have to — one way or the another.