Summary:
Having to write less code to implement a given feature often improves developer productivity: less code means less bugs, less tests to write, and less artifacts to maintain. Just as recent advances in rich-client technologies reduce boilerplate code on the client, new languages targeting the Java Virtual Machine can yield similar benefits on the server. This article illustrates how Flex on the client, combined with Scala on the server, results in a highly effective client-server development model. The article also shows a way to use the Java Persistence API (JPA) from Scala code.
The ability to add new comments in this discussion is temporarily disabled.
Most recent reply: August 5, 2009 0:51 PM by
Vince
|
|
This article shows that using Flex for a rich client with Scala for server-side code results in a highly effective client-server development model that minimizes boilerplate code. The article also shows a way to use the Java Persistence API (JPA) from Scala code. http://www.artima.com/articles/flex_and_scala.htmlWhat do you think of the approaches demonstrated by the article?
|
|
|
|
|
Great article!! I am in the process of switching from Groovy to Scala as my default service language for optimized Flex-based RIA projects. I would really like to see an application server fully embrace Scala's concurrent programming model, but for now I'll settle for the reduction in code and the general efficiencies Scala brings to the table.
|
|