Live data from Hacker News

Scala 2.11.0 Release Notes

scala-lang.org

11–20 of 77 posts

Re: Scala 2.11.0 Release Notes

#11
post #4

Probably the best change in my opinion was resolving the arity limit for case classes: https://issues.scala-lang.org/browse/SI-7296 I've bumped up against that limit pretty bad while trying to deserialize json. Shapeless did a lot to solve the problem, but I'm sure glad that limit has been removed.

I wish the same was done for tuples, but it wasn't and it's unclear whether that's even in plans.

Re: Scala 2.11.0 Release Notes

#12

Compared to 2.10 the 2.11 release is nothing special: some optimizations, bunch of bug fixes and deprecations (that hopefully lead to slash and burn of little used language features in 2.12). Curious to test out build times in 2.11, sounds like some minor gains have been made there, and more to come in the 2.11 release cycle as the new scalac optimiser is integrated ( http://magarciaepfl.github.io/scala/ )

[deleted]

Re: Scala 2.11.0 Release Notes

#15

Compared to 2.10 the 2.11 release is nothing special: some optimizations, bunch of bug fixes and deprecations (that hopefully lead to slash and burn of little used language features in 2.12). Curious to test out build times in 2.11, sounds like some minor gains have been made there, and more to come in the 2.11 release cycle as the new scalac optimiser is integrated ( http://magarciaepfl.github.io/scala/ )

That's really exciting to me. (So is slash and burn, though.) Give me another two years of compiler improvements, bug fixes, and IDE/tooling improvements!

I'm actually in a really good place IDE-wise, have a stripped down Eclipse (Platform + RCP build) with 2 Scala plugins, Scala IDE and Scala Worksheets.

SBT does the heavy lifting (have automatic build turned off in Eclipse) while Eclipse provides the dev environment.

Really snappy, zero spurious errors, it's like night and day compared to 3 years ago, woo hoo ;-)

Re: Scala 2.11.0 Release Notes

#17

I want to be writing scala so bad, but there doesn't seem to be any jobs in my area. Are there any scala specific job boards out there?

This is a tough one. I've started working with Scala full time by convincing my boss that this is the way to go. Let's just say without going into too much detail that I've proved my point, because our original stack now looks just miserable in comparison. From what I can see (at least in UK) Scala jobs are more of the high end ones and usually has to do with finances and/or "big data", which is why there aren't many of them. Also, I think Scala if not for everyone which is why it's usually used by someone who's more or less a seasoned professional mastered more than one language.

Re: Scala 2.11.0 Release Notes

#18

I want to be writing scala so bad, but there doesn't seem to be any jobs in my area. Are there any scala specific job boards out there?

I haven't seen any job boards specific to Scala, but there do seem to be more jobs popping up looking for Scala experience.

You could also work at evangelizing Scala in your current (presumably) Java shop. I've found success with this approach by getting other developers interested in the language and mentoring them, especially during the steeper parts of the learning curve. If you can pique the interest of a good portion of the development team it's often not too difficult to get a new language introduced through smaller non-critical or non-production systems, which is a good foothold with which to get the benefits visible to the wider group. YMMV of course.

Re: Scala 2.11.0 Release Notes

#19

Relevant: "Functional Programming Principles in Scala" starts in 4 days on coursera, which was created by the author of scala. https://www.coursera.org/course/progfun

I concur, this is a really good course. I've since switched to Clojure but I still think that I gained a lot from working through this course. It is a really great introduction into functional programming paradigms, and well worth it even if you don't plan to continue using Scala.

Re: Scala 2.11.0 Release Notes

#20
post #4

Probably the best change in my opinion was resolving the arity limit for case classes: https://issues.scala-lang.org/browse/SI-7296 I've bumped up against that limit pretty bad while trying to deserialize json. Shapeless did a lot to solve the problem, but I'm sure glad that limit has been removed.

I wish the same was done for tuples, but it wasn't and it's unclear whether that's even in plans.

Shouldn't that go hand in hand? The generated unapply method will involve a tuple of same arity I believe.
Post reply on HN