modersky

9 ms·

31.
by modersky 13y ago
The blog post and question is somewhat inflammatory (no wonder it gets upvoted so readily). Scala has been in category "adopt" in Thoughtworks Radar for a while now. http://www.thoughtworks.com/radar It's not
32.
by modersky 13y ago
Phil Bagwell was loosely associated with my group in 2000 but did not work for me then. His work at the time was theoretical; the first practical implementation is Clojure's. Scala's implementations only appeared in version 2.8, i
33.
by modersky 13y ago
It looks like you are right. Only enrolled students can see the material and enrollment is closed for the previous sessions. I'll check whether there's a practical way to make the material available.
34.
by modersky 13y ago
If you go on the course page https://www.coursera.org/course/progfun You see archives of the two previous iterations of the course. Their material is always available, and you can stream or download the videos from the
35.
by modersky 13y ago
Yes, sorry for the video :-) We had just 1 hour in the same place together, and that was in a hotel conference room and we were all tired from our respective conferences. We'll shoot another one when we meet next and will replace the v
36.
by modersky 13y ago
Yes, Gilles Dubochet crafted the Scala logo from these stairs.
37.
by modersky 14y ago
And, I should add, given this level of demand it's a good thing we just finished the Scala massive open online class with more than 10'000 developers completing the course with success.
38.
by modersky 14y ago
Just take absolute numbers: According to indeed, there are over 1000 open jobs mentioning Scala in the US, and over 750 in the UK. Taken together, the number of open Scala jobs in both countries exceeds the number of open Groovy jobs. It's
39.
by modersky 14y ago
It's true that this is not primarily a "learn Scala" class; we will concentrate on the purely functional subset. But types won't be omitted. We will focus on Scala's type system in week 4 of the class.
40.
by modersky 14y ago
Subtitles are being produced. They should be up in a day or two.
41.
by modersky 14y ago
The coverage at GigaOm provides a bit more substance. http://gigaom.com/cloud/typesafe-gets-14m-to-push-scala-as-a... And there's the Typsafe blog from the source: http://blog.typesafe.com
42.
by modersky 15y ago
I am very much aware of the double-edge sword nature of macros, and therefore follow and aid their progress with much trepidation. The single thing that sold be was that macros by themselves already could replace a compiler phase, which did
43.
by modersky 15y ago
Sorry for my misunderstanding regarding comments. I got frustrated by some recent Scala bashing posts that had comments disabled, and mistakenly assumed there was a pattern. I meant to respond directly to your blog, but now that the discuss
44.
by modersky 15y ago
I agree. Implicits don't compose transitively (and for good reason), and that makes them complex. That's why I suggested to think about putting implicit conversions behind a compiler switch. They are extremely useful for what they are but n
45.
by modersky 15y ago
I am thinking only of putting (some) definitions of implicit conversions behind a compiler flag. Uses of such conversions would remain unaffected.
46.
by modersky 15y ago
Arrays are not collections, either in Scala, or in the blog's condensation of it. But the blog nevertheless tries to define a single extension method that works for both sequences and arrays. I do not think this problem has a simple solutio
47.
by modersky 15y ago
Arrays are not sequences, in either the standard Scala library or his condensation of it. The goal is still to define a single extension method for two unrelated types.
48.
by modersky 15y ago
The author tries to add "ident" to Seq, and have it work automatically on native Java arrays.
49.
by modersky 15y ago
First, I think a blog post ending with "bring on the flames" should have comments enabled, otherwise it's not really fair. It comes across as whining without wanting to listen to advice or a response. Second, I think the blog post is useful
50.
by modersky 15y ago
The problem affects us not at all, as we build from source. The compatibility problem is a different one: Unlike almost everybody else, Scala IDE uses the standard Scala compiler in presentation mode. That compiler has undergone changes fro
51.
A First Taste of Akka 2 distributed Java/Scala middleware(blog.typesafe.com)
10 points by modersky 15y ago|0 comments
52.
by modersky 15y ago
I agree about the former state of the Eclipse plugin; that's why Typesafe has spent considerable resources in changing that. I encourage you to give a try to the current release candidate of Scala IDE 2.0: http://www.scala-ide.org
53.
by modersky 15y ago
This is right up there with most brilliant explorations I have seen in Scala. I am very pleased indeed that the language and its tools are strong enough to support that kind of experiment. It's a different question entirely whether you want
54.
by modersky 16y ago
That would go under bug fixes. But you could help us by filing tickets on trak. The general issue (type volatility) is well known, but you have discovered a loophole which wasn't.