What would be cool/interesting is if you can write half decent audio processing code in Go for Android without the GC kicking in at the wrong moment.
They're 100% right about the broader API though.
What would be cool/interesting is if you can write half decent audio processing code in Go for Android without the GC kicking in at the wrong moment.
They're 100% right about the broader API though.
I'd really love to see Google throw some serious engineering muscle behind Rust, with the long-term goal of making it the default first-choice language for Android development. I'm not holding my breath for this though.
The design of Swift was somewhat hobbled by ObjC/Cocoa legacy requirements but it's still much better language for native client development than Java, IMO. Sooner or later Google is going to need a better story here.
I'd be happy to be convinced otherwise by someone who knows more. :)
Since you are not forced to think about lifetimes, then you get memory leaks, double frees and dangling pointers, usually leading to crashes in totally unrelated locations or worse, security exploits.
Any language with automatic memory management, be it via dataflow analysis, RC or GC is managed.
http://blogs.unity3d.com/2014/05/20/the-future-of-scripting-...
Also XNA is reborn as MonoGame. Microsoft wants to decouple from it's APIs and tools by offloading to OSS and third party (Unity3d).
So this way C# got a foot on the door, long before XNA and Managed Direct X came into the picture.
Our client dev is all Unity, however, and I don't quite see Go entering our client dev cycle at all. And I'm a huge Go fan.
Having said that, I'm not at all interested in writing an app that was Android only so I'll be sticking with javaScript for a while yet.