Changes for page WebObjects with Scala

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,13 +1,13 @@
1	1	=== What is Scala? ===
2	2
3	3	Scala is a modern language not unlike Groovy.
4		-It is said to be more powerful and faster than Groovy or Ruby.
	4	+It is said to be more powerful and faster than Groovy or Rub.
5	5	This has been the reason for its adoption at sites like Twitter.
6	6
7	7	Many of its features and paradigms favor multi-threading and concurrency.
8	8	It could be said that Scala was designed from the ground up for concurrency.
9	9
10		-Some of these features may not be unfamiliar to Objective-C or WebObjects developers. Here's a summary:
	10	+Some of these may not be unfamiliar to Objective-C and WebObjects developers. Here's a summary:
11	11
12	12	|= |= Objective-C |= Java |= Scala
13	13	|= Mutable/Immuable Datatypes | Collections //e.g: NSArray/NSMutableArray// | No | Yes
...	...	@@ -30,10 +30,10 @@
30	30	With Web 2.0, building concurrent WebObjects applications is a must.
31	31	Developing and maintaining a concurrent or multi-threaded WebObjects application can be challenging.
32	32
33		-The lack of static variables means that Scala is inherently thread-safe.
34		-It has concurrency that is effectively built-in to the language in the form of Actors.
	33	+Scala offers concurrency that is (effectively) built-in to the language and is inherently thread-safe.
	34	+In other words, developing Ajax (i.e asynchronous communication) with WO will require concurrent request handling and thread-safe code, for which Scala is a better choice than Java.
35	35
36		-So for WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for concurrent applications.
	36	+In addition Scala offers itself as a solution for tasks that typically would have involved threads in a WebObjects application
37	37
38	38	=== Can WebObjects be Programmed In Scala? ===
39	39