On Mon, May 1, 2017 at 9:30 PM Tomi Häsä <tomi.h...@gmail.com> wrote:
> The situation with MIPS seems intriguing. There were promises of Android > MIPS devices for last year: > > > http://www.pcworld.com/article/2601040/first-mobile-device-with-mips-64bit-processor-coming-in-2016.html > > State of MIPS regarding Android could be quite dead, if you can trust this > discussion: > > > https://www.reddit.com/r/Android/comments/4ofdkv/state_of_mips_plus_some_statistics/ > > FWIW, Go itself added support for mips32 and mips64 recently, so adding Go Mobile support probably wouldn't be that much extra work. > I have stumbled upon mentions of different ARMv[number] discussions like > this one: > > > https://android.stackexchange.com/questions/34958/what-are-the-minimum-hardware-specifications-for-android > > Teaching the basics of processor architectures is probably off-topic on > the wiki page, but maybe there is a good introduction to processors like > ARMv5 (minimum for Android) somewhere? If I develop for Android 4+, maybe I > don't even need to understand processor architectures that much? > > No. AFAIK, every recent (4+) Android device is at least armv7 (or arm64). > The reason why I'm interested in using Go with Android is I just love the > simplicity of the syntax of Go. I could use Go instead of C/C++ (I have > programmed with C++) to add some security by accessing a database or > something else (save some key/value pairs instead of using Java), if that's > possible with Go + Android. What do you think about this approach? > > Sure. - elias -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
