Another thing that might help are some ideas about how to incorporate it into existing projects without having to gut the project or start over with a new one. If I have a big website, how do I add some new feature using Scala instead of Java. People still have to maintain old code but if adding Scala to an existing website is possible, then people may be willing to give it a try since the cost to do so is low. If they have to start over, then the cost to try is much larger and thus many will not be inclined to give it a try.
2011/6/12 Cédric Beust ♔ <[email protected]> > >>> Read it... bah. In tutorials everything is simple and clear, if the >> writer is skilled. It seems that All The Problems Of The World lie in >> parentheses and semicolons. The real world is another thing. The validation >> of Scala, if it comes, won't be in tutorials. Critical mass and good ROI are >> very relative and still volatile at this point. While if I look at my >> situation I'd say that I won't find a single customer to whom I could sell >> my hypothetical skills in Scala (but maybe it's because since I don't know >> Scala I don't search for Scala customers; OTOH I seldom have to search for >> Java jobs, they come spontaneously), the point is another: I still find lots >> of things that I don't know that would give a much greater ROI if I spent >> some time in learning them. >> > > Same reaction. Bruce seems to like becoming overly enthusiastic for a > technology every few years, I'm glad that at least he's recovered from his > dynamic typing infatuation :-) > > In my experience with Scala, it's hard not to like the language in the > first week and it's hard to still be in love with it after reading the 700+ > pages of a book about it, and I don't think Bruce's introduction is > particularly innovative. > > More specifically, showing that you can write "println("Hello world")" in > one line compared to Java is pretty underwhelming, especially since there > are so many areas where Scala shines over Java. > > I think a tutorial that would be much more likely to win over Java > developers would be one involving some fairly non trivial OO hierarchy and > showing how a judicious mix of traits, genericity and implicits can lead to > a much cleaner design than is possible in Java. > > -- > 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. > -- Robert Casto www.robertcasto.com www.sellerstoolbox.com -- 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.
