adriaanm

12 ms·

1. 61.▲
   by adriaanm 12y ago

   First off, macros are not just an advanced feature. They are experimental. Investments in tooling will always focus on official features first (not to say we ignore macros, but we have to prioritize). We spend a lot of time optimizing the c
2. 62.▲
   by adriaanm 12y ago

   (Scala tech lead here). We're doing everything within our means to improve tooling -- we agree it's crucial. Which changes would you like to see that aren't happening? One engineer on the Scala team (Grzegorz Kossakowski) spe
3. 63.▲
   by adriaanm 12y ago

   Do not underestimate the cost (time & $$$) of immigrating and the in(s)anity of US immigration law. Winning the H1b lottery is probably the easiest way. Getting a green card requires a pretty dedicated sponsor willing to spend $5-10K, n
4. 64.▲
   by adriaanm 12y ago

   We've been thinking about this a lot, even though Scala 3 is a couple of years out. Our current thinking is to bring the 2.x series as close to 3.0 as possible, with the remaining breaking changes being compelling enough to switch. Ple
5. 65.▲
   by adriaanm 12y ago

   To be fair, 2.10 introduced quite a few new features (my favorite being string interpolation). To name some more: implicit classes, value classes, language imports, reflection & macros,... 2.11 set the tone for the remainder of the 2.x
6. 66.▲
   by adriaanm 13y ago

   Thanks. I should add that dispatch has long abandoned their periodic table (before they got called on it last Scala Days, actually).
7. 67.▲
   by adriaanm 13y ago

   James Roper, my colleague, just wrote about Java 8 and Scala better than I could, so allow me to link to his post: http://jazzy.id.au/default/2013/03/28/java_8_lambdas_the_mis...
8. 68.▲
   by adriaanm 13y ago

   Sure, Scala is used for research, it came from research, but I don't think it's accurate anymore to say it's a research language. Some of our clients are doing some really cutting edge stuff, but I wouldn't call them res
9. 69.▲
   by adriaanm 13y ago

   Yep, scala's .net back-end is discontinued, and one of the main challenges (I worked on it a bit) was indeed generating the proper generic signatures. (I hear people are using ikvm these days.)
10. 70.▲
    by adriaanm 13y ago

    The search clipboard: cmd-e is to cmd-g as cmd-c is to cmd-v.
11. 71.▲
    by adriaanm 13y ago

    scala> val pi = "pie!" pi: String = pie! scala> println(f"Care for some $pi%f?") <console>:9: error: type mismatch; found : String required: Double println(f&
12. 72.▲
    by adriaanm 13y ago

    Awesome tech, but I don't see myself handing over my phone in a busy restaurant/bar -- you don't usually get to swipe your card yourself there.
13. 73.▲
    by adriaanm 13y ago

    Another example would be Scala. It has a command-line REPL and the IDE has a worksheet[1]. I find both tremendously useful. [1] https://github.com/scala-ide/scala-worksheet/wiki/Getting-St...
14. 74.▲
    by adriaanm 13y ago

    Macros were not developed by Typesafe, though we do try to help out. Also, macros are clearly marked experimental -- a compromise for a language co-developed by researchers (EPFL has invested over a decade in Scala) and industry. We (Typesa
15. 75.▲
    by adriaanm 13y ago

    Smooth upgrades between major Scala releases is one of our[1] two top priorities (the other being compiler performance). I disagree that "nothing" has happened since 2.8 to improve Scala's enterprise readiness (the Scala team
16. 76.▲
    by adriaanm 13y ago

    Check out https://github.com/scala/async
17. 77.▲
    by adriaanm 13y ago

    Really? The only image I get is a leopard print chevy with a hottub on a trailer.
18. 78.▲
    by adriaanm 15y ago

    I think it would be great if we could replace implicits by: 1) a simple mechanism for "enrichment" (aka. retro-active extension, virtual classes) 2) functional type-level computation (as opposed to the mini-prolog engine that is implicit se