by michaelty on 12/13/11, 12:05 PM with 69 comments
by nadam on 12/13/11, 1:39 PM
If 1/100th of the VC money going into social startups would go into actual technology companies, if it were an accpeted business model to sell (maybe read-only open source) technology for money, then the tech landscape would be totally different.
TL;DR: to replace Java, a lot of directed professional development effort would be needed: money would help a lot.
by cfontes on 12/13/11, 1:48 PM
Of course Java will always be around because it's easy to learn(I earn my money with it BTW) and it protects you from all kinds of stupid errors that newcomers could do in C , C++ or Javascript (memory management, Static Typed, etc...) but Scala provides a very flexible way to code a way that most Java devs are not used to, and therefor it takes a while to learn, but when you do learn it's a Joy I am a proof of that I really like coding in Scala while java is like my work horse, scala is what I use for my fun coding.
BUT... as an young language it have some major drawbacks, like lack of a proper IDE, slow compiling time, lack of Frameworks, lack of documentation and so on... but I am really happy to see Typesafe writing the problems down and fixing them when possible, it will take a while but when it's done it's going to be a very good language to know, and they are slowly I agree but fixing it.
by socratic on 12/13/11, 6:35 PM
I had been thinking of Scala as though it was Java++ (in analogy to C vs C++): a language that adds a few features on top of Java for better abstractions, but regular Java programmers can basically program Java in it (and read it as though it was Java). However, it seems like truly idiomatic Scala code involves heavy use of advanced functional and type system concepts that cannot simply be glossed over.
Will Scala and/or Clojure end up as languages in the JVM used by a small number of senior developers to be more efficient on particular problems (like F# on the CLR) rather than the next big language used by everyone (like C++ superseding C for most problems)? And, is that an accurate portrayal of how F# is currently being used?
by mgkimsal on 12/13/11, 1:23 PM
Probably all "alt.java" tech will remain somewhat fringe, simply due to inertia. And although I wasn't in the Groovy community at the beginning, I do think that Groovy, in some small part, helped further along the "non Java on the JVM" story, giving people solid examples of using alt.java languages without having to leave the JVM altogether.
by philjackson on 12/13/11, 1:58 PM
"Ridicule about parallel collections in 2.9 (one of its major new features)"
by pvillega on 12/13/11, 1:40 PM
by tutysara on 12/13/11, 5:31 PM
by DannoHung on 12/13/11, 5:58 PM
And those were not written to be used with Scala.