I remember I couldn't finish watching that video, not because of the content, but due to the way he was presenting it. It was just too disturbing to watch... Don't do that guys...
Yeah, his emotions were so intense for him that it was hard to watch. I definitely get it; if you're going to spend 80-hour weeks for 5 years on something mainly because you like it, you have to be pretty intense. But it's a double-edged sword; now his grief and loss and sense of betrayal are very intense too. It was very raw.
In case others are curious as to content: For me the major takeaway was that the person who has written more core Scala code than anybody thinks that the collections and probably the whole language is irredeemably fucked. He had example after example where if you do a reasonable action in 2 different ways, you get 2 different results, and that it was impossible to know why without an incredibly deep understanding of the implementation details.
This makes me sad, as I really like a fair bit of what Scala does. But the video makes a persuasive case that Odersky, et al, bit off more than could be chewed, throwing in too many interesting ideas without really thinking through what happens when those ideas intersect and combine.
Comments
Going by Paul Phillips's (largest contributor to the scala compiler) YouTube rant, https://m.youtube.com/?#/watch?v=4jh94gowim0, nobody ever gets over the cliffs.
His rant is great, for more than just scala.
Wow. Just starting to watch, but my first thought is: thank goodness he got to give this talk when he did; otherwise he might have exploded.
The link that works for me on a desktop browser: https://www.youtube.com/watch?v=4jh94gowim0
And here are the slides: http://www.slideshare.net/extempore/a-scala-corrections-libr...
Wow, this is a brutal talk.
I remember I couldn't finish watching that video, not because of the content, but due to the way he was presenting it. It was just too disturbing to watch... Don't do that guys...
Yeah, his emotions were so intense for him that it was hard to watch. I definitely get it; if you're going to spend 80-hour weeks for 5 years on something mainly because you like it, you have to be pretty intense. But it's a double-edged sword; now his grief and loss and sense of betrayal are very intense too. It was very raw.
In case others are curious as to content: For me the major takeaway was that the person who has written more core Scala code than anybody thinks that the collections and probably the whole language is irredeemably fucked. He had example after example where if you do a reasonable action in 2 different ways, you get 2 different results, and that it was impossible to know why without an incredibly deep understanding of the implementation details.
This makes me sad, as I really like a fair bit of what Scala does. But the video makes a persuasive case that Odersky, et al, bit off more than could be chewed, throwing in too many interesting ideas without really thinking through what happens when those ideas intersect and combine.