News for hackers. Stuff that matters.
Re:Why Android should switch to Go by jzs on Tuesday May 15, 2012 @12:48PM (#3977416)
While i truly love Go as a language i think it might still not be mature enough to be used as a full fledged language for Android. The garbage collector is still not mature and could use some optimizations.

You also call Java a systems language. I'm not sure i agree in that view since you don't have direct access to the hardware it runs on. You're still running on JVM which does jit compilation of your code. Java is a high level language falling into the came category as the .NET languages and Python.

I would still very much see Go on android as a fully supported language. Go is beautiful.

Re:Why Android should switch to Go by stcredzero on Tuesday May 15, 2012 @01:55PM (#3977794)
The garbage collector is still not mature and could use some optimizations.

For mobile, I'd use reference counting, with an incremental collector working on the cycles. (And encourage the pros to use weak references.)

Re:Why Android should switch to Go by pcwalton on Tuesday May 15, 2012 @04:32PM (#3978656)
I'm skeptical. Incremental cycle collection is quite hard, and you lose the benefits of cycle collection (only tracing suspected-dead objects) when you move to tracing garbage collection as a backup for reference counting.

For mobile I would just use an incremental garbage collector with heavy usage of stack allocation and interior objects. Or use a reference-counted system and disable the GC entirely (leaking cycles).

Re:Why Android should switch to Go by stcredzero on Wednesday May 16, 2012 @10:28AM (#3982151)
Incremental cycle collection is quite hard

Incremental GC has been done. It wouldn't be super efficient, which is why one would encourage the pros to use weak references.