Psp collections: views and more by Paul Phillips
Why Hacker News recommends it
Cited in Scala debates as an insider's critique that persuaded many the language's problems were deep.
What it is
Paul Phillips, a major Scala compiler contributor, gives a long talk on Scala collections and views, using it to critique Scala's design and direction.
Recommended by 2 HN commenters across 2 different months, 2014 to 2018.
What Hacker News said
Recommends laureny · 2014-02 · on “Why not inherit from List?”
> Or use a better language ;-). E.g. in Scala You might want to watch Paul Phillips' recent talk: [this video] You will probably start changing your mind about whether Scala is a "better" language. Especially on the collections side. > to get all the benefits without the drawbacks of Java style subtyping. Actually, the Scala collections have the exact same problems caused by subtyping that Java does (and quite a few more actually, as Paul explains).
Recommends bjwbell · 2015-09 · on “Bruce Eckel announces he's going to write Atomic Python”
Going by Paul Phillips's (largest contributor to the scala compiler) YouTube rant, [this video] , nobody ever gets over the cliffs. His rant is great, for more than just scala.
Cites wpietri · 2015-09 · on “Bruce Eckel announces he's going to write Atomic Python”
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: [this video]
Cites piokoch · 2015-11 · on “Five years of Scala and counting: debunking some myths”
I am curious to what extent Paul Phillips lecture [ [this video] ] is just a rant or in-depth Scala criticism. If he's right then seems that we should not expect bright future for Scala. I am wondering what Scala experts would say (I don't know Scala sufficiently to trust my judgment)?
Critical laureny · 2014-03 · on “Scala 2.11.0-RC1 is now available”
> Prof Odersky has been quite vocal about the feature bloat and lets hope the future releases are more conservative in that sense. Languages never get simpler as they age, and Scala is certainly proof of that rule. If anything, advanced features that make up for good academic papers have priority over fixing bugs and streamlining the libraries. Paul Phillips, a Typesafe cofounder, recently left the company and went on a tour explaining why he thought Scala was headed in the wrong direction: [this video]
Critical turar · 2014-05 · on “An Opinionated Guide to Modern Java Development, Part 1”
I actually started learning Scala: completed Odersky's Coursera class and developed a Play 2 project in Scala. Overall I like it, but reading others' code is often frustrating, shorthand shortcuts in language are still kinda alien looking, and even figuring how to handle simple things like multi-file upload with Play's controllers, I feel I don't quite understand what the hell is going on underneath all that magical functional code that I myself wrote by assembling bits and pieces from elsewhere. And then I watch stuff like Paul Phillips presentations [ [this video] ] and I just don't know whether continuing to invest my time in Scala is a wise decision long-term. I'll probably try Clojure at som
Critical wpietri · 2016-06 · on “Ask HN: What is your experience with Scala?”
I took Odersky's online course and used it for one project. It runs my home lighting system. My experience was definitely mixed. I liked the language for its ambition. I think the notion that OO and functional approaches are complementary worked very well for me. There were a lot of interesting ideas in the language and the ecosystem. However, there were a number of downsides. I came across a couple of bugs that were well known and apparently people were just expected to work around them. As others have said, compile times were terrible, and the tooling wasn't great. And at a one day Scala unconference one of the prominent Scala community members was a flaming asshole to me, which definitely
Critical wpietri · 2018-04 · on “Towards Scala 3”
Could you (and perhaps others) say more about this? I was excited to read that key goals were simplification, clarification, and consolidation. But my exact worry is that they didn't go far enough. I liked the idea of Scala and took Odersky's course. But I built a few things in it and it was never not frustrating. What Bruce Eckels said resonates with me: "I’ve come to view Scala as a landscape of cliffs – you can start feeling pretty comfortable with the language and think that you have a reasonable grasp of it, then suddenly fall off a cliff that makes you realize that no, you still don’t get it." Then I watched this Paul Phillips talk, which convinced me that the problems were deep, not s