Skip to Content

Changes for page WebObjects with Scala

Last modified by Ravi Mendis on 2011/05/10 02:10
From version 400.1
edited by Ravi Mendis
on 2010/01/17 22:07
Change comment: There is no comment for this version
To version 402.1
edited by Ravi Mendis
on 2010/01/17 19:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,9 @@
1 1  === What is Scala? ===
2 2  
3 +Scala is a modern language not unlike Groovy.
4 +It is said to be more powerful and faster than Groovy or Ruby.
5 +This's been the reason for its adoption at sites like Twitter.
6 +
3 3  Scala is a language for concurrent computing.
4 4  In the day and age of multi-core processors, concurrent computing can't be ignored.
5 5  
... ... @@ -26,12 +26,13 @@
26 26  
27 27  === Why Use Scala? ===
28 28  
29 -Scala is inherently thread-safe.
30 -Because of the lack of static variables developers don't need to worry about synchronising access to mutable shared data.
31 -It has concurrency that is effectively built-in to the language.
33 +Developing and maintaining a concurrent or multi-threaded WebObjects application can be challenging.
32 32  
33 -So for WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for concurrent applications. (In other words, Scala Actors can be used for problems that would have normally required threads).
35 +The lack of static variables means that Scala is inherently thread-safe.
36 +It has concurrency that is effectively built-in to the language in the form of Actors.
34 34  
38 +So for WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for concurrent applications.
39 +
35 35  === Can WebObjects be Programmed In Scala? ===
36 36  
37 37  Yes. It is very simple.