4 ms·

I see similar work has been done for Scala. Amongst other things: https://code.google.com/p/scalaforandroid/ https://code.google.com/p/scalaforandroid/ Does

by 616c 13y ago

I see similar work has been done for Scala. Amongst other things: https://code.google.com/p/scalaforandroid/ https://code.google.com/p/scalaforandroid/ Does anyone with Scala on Android experience know if it is bogged down by the same size and performance issues? I assume they are running against the same problems on parallel tracks. Just curious.

wiradikusuma 13y ago
I'm a Scala guy learning Android. There's Scaloid which offers more concise way of doing things, but now tools (esp. Android Studio) are getting better for XML (and faster feedback thanks to live preview), so now I'd rather take the XML route (although probably as I'm getting more proficient with Android, I would prefer programmatic). The performance is not bad. ProGuard is a must. The problem for me is compile time.
jbrechtel 13y ago
It's not bogged down by the same performance. There may be times where idiomatic Scala code generates more garbage than similar Java code and thus has more of an impact on Dalvik performance but these are straight forward to work around and well understood. For the vast majority of apps this isn't a problem. Scala does suffer a similar size issue where the Scala standard library is a few megs and you don't really want to ship that around with your app. You can use ProGuard to strip out the parts of the Scala standard library you aren't using. This is baked into build tools (like jberkel's excellent android-plugin for sbt) so it's usually seamless. FWIW, I've got a couple Android apps on the Play store written in Scala.
DanielRibeiro 13y ago
I've been using Scala to develop for Android for a while. There is this sample project to get you started with nothing Java, Ant and the latest Android SDK required: https://github.com/danielribeiro/HelloScalaOnAndroid https://github.com/danielribeiro/HelloScalaOnAndroid

by 616c 13y ago

wiradikusuma 13y ago

I'm a Scala guy learning Android. There's Scaloid which offers more concise way of doing things, but now tools (esp. Android Studio) are getting better for XML (and faster feedback thanks to live preview), so now I'd rather take the XML route (although probably as I'm getting more proficient with Android, I would prefer programmatic). The performance is not bad. ProGuard is a must. The problem for me is compile time.

jbrechtel 13y ago

It's not bogged down by the same performance. There may be times where idiomatic Scala code generates more garbage than similar Java code and thus has more of an impact on Dalvik performance but these are straight forward to work around and well understood. For the vast majority of apps this isn't a problem. Scala does suffer a similar size issue where the Scala standard library is a few megs and you don't really want to ship that around with your app. You can use ProGuard to strip out the parts of the Scala standard library you aren't using. This is baked into build tools (like jberkel's excellent android-plugin for sbt) so it's usually seamless. FWIW, I've got a couple Android apps on the Play store written in Scala.

DanielRibeiro 13y ago

I've been using Scala to develop for Android for a while. There is this sample project to get you started with nothing Java, Ant and the latest Android SDK required: https://github.com/danielribeiro/HelloScalaOnAndroid https://github.com/danielribeiro/HelloScalaOnAndroid