HN Explorer

12 comments

[ 1.9 ms ] story [ 41.3 ms ] thread
mark_l_watson
Cool. I've been writing Scala and Clojure wrappers for a larger Java project, and I ran into a minor hassle last week with Scala/Java integration and I read something that indicated that things would be easier with Scala 2.8. I am downloading the beta right now to see if there are any problems using it with InteliJ 9.
mark_l_watson
Trying 2.8 did break some of my code (as expected from reading the 2.8 beta docs)
Confusion
Scala/Java integration will always be somewhat of a problem, that requires thought and effort to get right. Any default way of converting between classes will leave some people going "WTF?". Jorge Ortiz's scala-javautils[1] can be helpful. Googling for these utils will lead to some blogposts discussing the problems of fully automatic conversion.

[1] http://github.com/jorgeortiz85/scala-javautils

kashif
This language makes me unhappy.
andrew1
Care to elaborate?
kashif
No not really - it isn't a concrete thing, its like a gut wrenching feeling you get when you look at a lot of clever C++/Perl code.
kashif
Apparently expressing emotion is bad
sreque
I haven't been this excited about a new programming language version in a long time. It almost feels like a bigger deal than the change from Java 1.4 to 1.5!
wheels
Named and especially default arguments is the win for me. I couldn't bring myself to start ripping out our Java code just to have to do all of the same silly method duplication all over the place.
samdk
For me, too. I learned Scala for a project last semester and named/default arguments were the one thing I missed the most.