On Dec 27, 6:11 pm, "Robert Lally" wrote:
>
> Tony has operator privileges on #scala,
That's because, AFAIK, he started that channel.
> With this, he is a significant and
> influential member of the Scala community and sets the tone for much of the
> IRC conversation. Feel free to insert you
James,
Thank you for your explanation. This was very helpful for me to get a better
understanding of some of the confusing nomenclature between Java and Scala, as
did the Moors, Piessens, Odersky paper that's been linked to previously
(http://www.cs.kuleuven.be/~adriaan/files/higher.pdf).
I
As someone who strongly believes that the community associated with a
language is the most important factor when it comes to determining how,
where and when that language will gain traction I had to chip in on this
thread.
Tony has operator privileges on #scala, and he uses it to ban those who
dis
for (int x=0;x < 3;x++) { wii.wish(U).merry(OS_X-MAS) } && happy = new
Year();
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to javaposse@googlegroups.com
To
Tony's um...debating style shouldn't be taken as reflecting the Scala
community in general.
To the topic at hand: Scala has only a few things are are genuinely
foreign to Java programmers. For instance, except for non-local
return, Scala's lambdas are really just a shortcut to writing certain
ki
I was thinking on how I would use Scala *right now* at work, in less
to more intrusive order:
1) Use Scala and ScalaCheck to create better unit tests for java code
(nobody needs to know I'm using Scala)
2) Create service modules and export them as jar libraries (just
import a couple of jars in the
