4 ms·
When Go came out in 2009, Android was only 2 years old. Go was easily not mature enough. Another consideration is Android was fighting for market share from Ap
by AncientPC 14y ago
When Go came out in 2009, Android was only 2 years old. Go was easily not mature enough.
Another consideration is Android was fighting for market share from Apple. Forcing Go on developers would just create another barrier to switching.
Go's ARM compiler (5g) still needs quite a bit of work before it can be used on Android. Right now, even the canonical "Hello World" program fails to work on a lot of Android phones.
There is too much momentum behind Dalvik that it would be near suicide to discontinue support. However that doesn't mean Android can't support both Java and Go in the future, but there must be a compelling reason to switch.
- Bjartr 14y agoSince dalvik is a vm, how likely would a go->dalvik bytecode compiler be?