Scala Collections: Why Not?

Channel:InfoQ · Length:45:41 · Published:2014-01-29 · Views:43205

Watch on YouTube

Summary

Paul Phillips, a Typesafe co-founder and prolific Scala committer, explains why he walked away from Scala. He critiques the Scala collections library and presents his own design focused on immutability, performance and correctness.

Why HN recommends it

Cited in Scala-skeptic arguments as an insider's critique, and for his alternative collections API design.

Programming language design · Functional programming · Software architecture & design

Subtitles (excerpt)

Hello. Uh I'm Paul Phillips. Um I gave a variation of this talk last night and the audience uh looked like like shell-shocked. Genuinely, they looked like they'd been through a war. And uh I realized so I think I'm going to tone it down tonight. Um yeah, no, you're you're all disappointed. I I think I one of those a week is probably good. You got to come to If I'm going to do back-to-back nights, you got to come to the first one if you want the exciting stuff. So, I'm going to be all chill tonight. But on the other hand, I'll probably not actually be able to hold to that, but I'll try. Um yeah, so my slides, I'll just tell you up front are pretty bad. They're all over the place. I don't know what's going on. We're just going to have to live with a Think of it as one of those non-linear narratives, like Quentin Tarantino movie or something. So, some suddenly something happens late that should Wait, isn't that Yeah, okay. So, it's non-linear. Um but you know, so we have this little stable of maybe 10 programming quotes that get recycled indefinitely, and this is one of them. Uh and but it's good and I'm going to read it. When I'm think When I'm working on a problem, I never think about beauty.

On Hacker News

> I don't want .Where() called on an array to return another array. I want a lazy IEnumerable<T> almost every time. Yes, good point. There is a lot of space to explore in collections API designs, and the LINQ design is just one of them that makes its own tradeoffs (e.g., only have to implement "GetEnumerator()" to get a watered-down monadic experience). Contrast that with the well-meaning but con… — harveywi, 2016-08
Before choosing Scala I think you should watch this talk: [VIDEO] (note: he's not a troll, he worked 5 years with Scala) — siwatanejo, 2020-11
I think all technologies have sharp edges somewhere, and the way to stay afloat in this business is staying alert. Testing assumptions help, be it through quick REPL experimentation or a unit test. JavaScript has some bad fame around unintuitive behavior but you can find these styles of issues in most languages. A random example: Scala. [VIDEO] — partycoder, 2017-04
If you enjoy these types of compiler videos then I would highly recommend the following rants against Scala by Paul Phillips (from TypeSafe and one of the core language contributors). He also talks about wanting to edit abstract syntax trees directly: [LINK] [VIDEO] — arkadiyt, 2015-05
(throwaaway here) Before you waste the next few months of your life learning a corrupt programming language: - Typesafe co-founder quits: [VIDEO] - [LINK] : Paul Dix - Why Node and Scala will dry up: Go will drink their milkshake - I can personally tell you, scala is awful at handling large codebases and is so filled with idioms, you have a difficult time reading it. I remember opening scala code… — throwawuy222, 2015-04

Related videos