adriaanm

9 ms·

31.
by adriaanm 10y ago
I'd love to turn off write-access to JIRA and move to GitHub for new tickets. We'll get there, but first need to finish this release everyone's waiting for :-)
32.
by adriaanm 10y ago
Hi, Scala Team Lead at Lightbend here! We are working hard on getting 2.12 out. Almost ready! While the theme for 2.12 is easily summarized (Java 8), I assure you the changes behind the scenes go all the way to the core. Compiling lambdas a
33.
by adriaanm 11y ago
SF killed it by not giving them parking permits: http://www.bmwblog.com/2015/10/05/drivenow-to-suspend-operat... > The company says the decision was influenced by the lack of parking permit regulations nec
34.
by adriaanm 11y ago
Exactly. The type checker does track constants (`false` internally has type `Boolean(false)`), but it won't drop `if` branches. That happens later, as you can see in the (abridged) output of `scalac -Xprint:all -Xprint-types`: [[sy
35.
by adriaanm 11y ago
You don't have to trust us (though you can -- trust me :-)). Take a look at the source, check some references of happy Scala users. Submit a PR to fix what you don't like. Ask a question on our forums/stack overflow. Whatever
36.
by adriaanm 11y ago
Paul's a perfectionist. Sure, the collections aren't perfect, and we will continue to improve them, but you should keep some background in mind when watching that video: he was pretty frustrated with issues in Scala development no
37.
by adriaanm 11y ago
(Scala team lead @ Typesafe here). Thanks for the kind & insightful words! We absolutely want to resolve the issues you're referring to, and we welcome everyone's help and input to speed up this process. We're working on
38.
by adriaanm 11y ago
Hi! Typesafe Scala team lead here (formerly in Martin Odersky's lab, where I implemented type constructor polymorphism aka "higher-kinded types" in 2007 and rewrote the pattern matcher in 2.10, before joining Typesafe in 2012
39.
by adriaanm 11y ago
As the Scala tech lead, I'm glad to learn we've finally adopted "almost every new PL concept!" I guess by now everyone will recognize your username and adjust for bias accordingly, but still, how about sticking to the fa
40.
by adriaanm 12y ago
(Hi, Scala Tech Lead at Typesafe here.) The Scala landscape is pretty far off from the node/io fork, I think. First of all, we are keen to keep Typelevel Scala and the official Scala distribution in synch. We're also seeing a heal
41.
by adriaanm 12y ago
Thanks! Please don't hesitate to ask (ideally on scala-internals) if you'd like some pointers to get started with abide.
42.
by adriaanm 12y ago
We've been working on https://github.com/scala/scala-abide . Our aim is to provide a nice platform for others to develop and distribute style checking rules. We (the core scalac devs) intend to focus on keeping the
43.
by adriaanm 12y ago
Sorry to hear that. It's a lot of work and the Scala team at Typesafe is pretty small. We welcome all the help we can get, but we're focussed on solving exactly these issues. If you'd like to get certain bugs prioritized -- w
44.
by adriaanm 12y ago
Thanks for clarifying. I understand your concern. The Scala side of our commercial offering aims to alleviate those worries. Please get in touch if you'd like more details on that.
45.
by adriaanm 12y ago
(Scala tech lead at Typesafe here) > Scala had its time, and I was a frequent user, but now I am not sure where it is going. It certainly helped bring functional programming into my vocabulary, and into a lot of other developers' to
46.
by adriaanm 12y ago
Thanks for pointing all this out. I honestly don't think of the Scala brand as being tied to the Play framework. Typesafe actually pushes Play on Java more than it does Play on Scala (even though we think Scala is better suited, obviou
47.
by adriaanm 12y ago
No, you'll have to review the patch yourself. We also don't indemnify you when we introduce a regression. We do have support contracts for those who want the fastest turnaround in fixing those...
48.
by adriaanm 12y ago
The warning is already there: -Xfuture -deprecation. We decided to delay making it a plain deprecation until we have said tool to do help you stay deprecation-warning-free. You are addressing deprecation warnings in a timely fashion, yes? :
49.
by adriaanm 12y ago
No, but omitting a return type for a non-private or implicit member is definitely a style violation.
50.
by adriaanm 12y ago
What's the alternative, though? By offering a nicely integrated platform, I would hope the community benefits from the halo effect this has on Scala. Our goal is to make the whole Scala eco-system successful, but we have to pick carefu
51.
by adriaanm 12y ago
I agree with most of your comment. Thanks for writing it down! First, the agreement: Yep, structs are a VM thing. We are very excited about Project Valhalla ( http://cr.openjdk.java.net/~briangoetz/valhalla/ etc).
52.
by adriaanm 12y ago
I believe that would be https://twitter.com/jddarcy/status/493137546814042112
53.
by adriaanm 12y ago
We do take compatibility seriously. Others have given examples in this thread how we do this technically. I don't think any design process can guarantee perfection at first try, hence we prefer steady improvement over stagnation. When
54.
by adriaanm 12y ago
There's Scala 2.9 (and older) code out there in production. Maintenance for older versions can be had.
55.
by adriaanm 12y ago
> Scala [...] only [used] by startups That is not what we are seeing...
56.
by adriaanm 12y ago
Thanks, happy to hear it!
57.
by adriaanm 12y ago
This is where IDEs and sbt's ~compile come in handy. I don't hit build very often, since the IDE tells me about my mistakes interactively, and, once it's happy, a build makes for a great micro-break :-)
58.
by adriaanm 12y ago
The changes as seen from the outside will be much more conservative than that. We're not ready to comment on specifics yet, but the main focus is to remove warts (deprecating them in 2.12/2.13 first where possible), make the type
59.
by adriaanm 12y ago
The Scala 2.x series is for source compatible releases. The goal is that you can just recompile your Scala 2.11 code on Scala 2.12. (As was the case for the upgrade from 2.10 to 2.11 -- modulo some changes necessary for important bug fixes.
60.
by adriaanm 12y ago
I see Java 8 more as an even better gateway drug to Scala than Java 6, so I expect adoption to accelerate. (Then again, I'm biased.) Java-8-the-language is a pretty timid comeback. Functional programming is not just about lightweight s

More ›