[this is a reply to three people, sorry if it looks like I'm misquoting] Scala is slower to compile because the compiler has more work to do, because the programmer has less work to do.
That said, SBT does seem to make the difference in compile speed disappear, though I haven't tried it in the large yet. I don't think Scala has any pathological compile times (i.e., programs that take a disproportionate amount of time or memory to compile), it's just a bit slower than Java. People are always bitching about maven too, but in general in #scala we have more experience with maven than with SBT. If you went back 2 years you'd see a lot more moaning about maven, at least from me! > All functional languages encourage immutability, and Scala isn't > different in that. Scala isn't functional. It's a hybrid. Saying it's functional without mentioning the other half is like those adverts saying that an oven costs <font size="infinitessimal">from</font> £200. Most importantly, Scala gives you no way of visually or even programmatically distinguishing functional from imperative code. But then it probably couldn't while maintaining its excellent level of Java interoperability. > Also, forget a reliance on actors or immutability. Going back to > Dijkstra's view on gotos "[we should do] our utmost best to shorten > the conceptual gap between the static program and the dynamic process, > to make the correspondence between the program (spread out in text > space) and the process (spread out in time) as trivial as possible," I > can't help but think continuations are going to be the "killer > feature" in the coming concurrency fun. (If I'm not mistaken, C# just > got them.) Sweet Jesus, I think I need a syntax-highlighting email client to see which parts of that were written by Dijkstra and which were written by you! :) -- 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.
