On Wed, Mar 30, 2011 at 3:36 AM, Kevin Wright <[email protected]>wrote:
> >>> Scala's very much in use around the world, there's a nice list on Quora > here: > > http://www.quora.com/What-startups-or-tech-companies-are-using-Scala > I like to think that whenever a technology takes the time to maintain a list of where it's used, that technology is actually not doing too well. Good luck finding such a list for Java, C# or C++. I'd say that 2.9 (currently a release candidate) is going to mark the > transition from early adoption to the first mainstream users. Most > importantly, the eclipse support has now reached a level that tooling should > no longer be a reason to not use it > Even Martin seems to disagree with you about this. > Java has had a long time to build up adoption, then came hibernate and > spring which have also been around a while. Groovy was the first of the > non-Java JVM languages, so it has a head-start some degree of commercial > support (not least, via Spring), so it's unsurprising that it currently has > higher adoption. > I shouldn't be surprised any more to see you throw facts that are not just completely wrong but not even researched, but it still never ceases to amuse me. Groovy 1.0 was released in 2007<http://en.wikipedia.org/wiki/Groovy_(programming_language)>and Scala 1.0 in 2003/2004 <http://en.wikipedia.org/wiki/Scala_(programming_language)> . > Scala, Clojure, etc. are all relatively young in this space and have yet to > realise their potential, though growth rates are impressive. > Ah yes, that's another Litmus test of a struggling technology: citing growth instead of actual mindshare. Growth means absolutely nothing since it's obviously trivial to grow at a 100% rate when you have 1% mind share. > It's also interesting to note that James Strachan is now an active > participant in the Scala community: > > * > http://macstrac.blogspot.com/2009/04/scala-as-long-term-replacement-for.html > *<http://macstrac.blogspot.com/2009/04/scala-as-long-term-replacement-for.html> > * > * > *Though my tip though for the long term replacement of javac is Scala. I'm > very impressed with it! I can honestly say if someone had shown me the > Programming in Scala book by by Martin Odersky, Lex Spoon & Bill Venners > back in 2003 I'd probably have never created Groovy.* > > > As for big important projects, Akka is undoubtedly the current one to > watch. > Akka is certainly a remarkable piece of technology, even more so since it offers both a Java and a Scala API. As to whether it will really make a difference in Scala's growth, color me skeptical. -- Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
