Linked by Thom Holwerda on Tue 7th Jul 2009 13:40 UTC
Thread beginning with comment 372169
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
@michaelg,
I think Scala on Android is a wonderful idea. I am an iPhone developer but a newbie to both Java and Android. Though I like developing for iPhone, we don't have choice other than Objective-C. Being able to choose is always a good thing.
Yours is a great article, I just wish there is more info on how to build the Convertor example with Eclipse/ADT/Scala plugins for a newbie like me,
. I am trying to follow the direction on
www.scala-lang.org/node/160 , but it might be dated, my eclipse IDE keeps crashing.






Member since:
2009-07-07
Glad you read the article! Scala has a lot of powerful features. However, it is very much an a la carte language. You don't have to use those features. You can write very Java-ish code in Scala, only you will write a lot less of it thanks to type inference, case classes, etc. After awhile you may venture out to using things like closures, multiple inheritance, operator overloading, and pattern matching.
Back to the article... I must disagree with the "exotic" assessment with regards to Scala on Android. Not only do you get all of the basic benefits of Scala over Java, but there are certain aspects of UI development that really benefit from Scala. I gave a couple of examples of this in the article: using a closure to handle a button click event and using pattern matching to handle menu selection events. There are many other things like this. I started an open source project with the purpose of sugaring the Android APIs using Scala: http://code.google.com/p/scala-android/ .