Viewing profile — adriaanm

This guy has an agenda. I would check his numbers yourself.

Ditto. I just moved from the Bay Area to Lausanne for many of the same reasons (except the vacations: still working for the same awesome employer).

+1 I use them in Lausanne. 777 CHF/year is a great deal! Interesting model: the price is the same for everyone, while bandwidth is the maximum they can offer in your location. Exce…

Good to hear! I agree :-) It was a necessary transition because we need to keep attracting customers that initially are reluctant to invest in Scala training. We've found our Java …

> Typesafe->Lightbend transition The renaming never affected the staffing of the Scala team at Lightbend -- we've been doing about 2/3 of core Scala development (major thank you to…

> I am reluctant in part because Scala.js does not quite have financial support of Lightbend. Or so it seems, it's a bit hard to tell where Lightbend ends and the non-profit Scala …

Procedure syntax (the last two lines, lacking the `=`) will be deprecated in Scala 2.13. The two variants before those are due to type inference. Are you really arguing against typ…

Thanks for your balanced reply. Sadly, some people see it as a badge of honor to write super clever code that's essentially write-only, and Scala somehow triggers this in them :-) …

[Scala team lead at Lightbend here] I'm always eager to learn how we can improve Scala, especially as we kick of the Scala 2.13 cycle (hard at work on compiler performance and stan…

Thanks, glad you like it! We at Lightbend (my employer) don't think of ourselves as very corporate, but we definitely sponsor Scala development. My team is hard at work on Scala 2.…

Which non-orthogonal and/or incoherent features do you have in mind?

The only thing on your list on your blog [1] that's still true is that we care about PL research. Since 2.10, we've worked really hard on improving the migration between major vers…

With scala async, you can also express this in direct style: https://github.com/scala/async .

Yep, 2.11.9 is the last planned release, but we would release another one for security fixes or anything as severe. If we get customer requests for backports, we (usually) also rel…

Thanks for the example. We agree that this is a tricky part in the collections. For Scala 2.13, our headline feature will be simplifying/refining the collections API. One of the ar…

I see how people might look at how close java & javax are, and think scala & scalaz are equally close. They are not. Scalaz is a completely separate project from the core Scala pro…

As the Scala team lead at Lightbend, I'm truly saddened to see posts like this. It couldn't be farther from our intentions and interests! We absolutely want outstanding Scala docum…

None of this makes any sense to me (except that these unfounded claims are not charitable). Lightbend (my employer) builds our whole platform in Scala, and we are proud to say you'…

True Scala 2.12 generates byte code that requires a Java 8 VM. Scala 2.11 will be supported for a while longer, with as many as the 2.12 features implemented there first (those tha…

Keen eye! The release is tagged and the artifacts are indeed on maven central, but we are holding the official announcement for a few days to be able to launch with a nice set of c…

In addition to being supported by the community, we (Lightbend) offer commercial support for Scala 2.11. If you're paying Oracle for Java 6 support beyond its EOL, perhaps you'd be…

Yes, if you're tied to Java 6, you're also tied to Scala 2.11. Why is the former version peg ok but not the latter? We do everything we can to enable 2.11.x maintenance by the comm…

The code emitted by 2.12.0-M5 is slower in certain benchmarks, but I don't expect this to be the case for the final 2.12 release. We're working on the performance issue, with help …

Hi, Scala team lead at Lightbend here (I left academia in 2012 to lead the team). We dropped Java 6 because we did not anticipate any business case for it, based on surveying our c…