4 ms·
The rant is mostly about the Scala collections API. I think the "expert" opinion is that yes, Scala collections are broken and incredibly complex, and theres a
by bonobo3000 11y ago
The rant is mostly about the Scala collections API. I think the "expert" opinion is that yes, Scala collections are broken and incredibly complex, and theres a proposal for new implementations here:
https://github.com/lampepfl/dotty/issues/818 https://github.com/lampepfl/dotty/issues/818
I think the talk was pretty influential, but atleast the community is responding. I don't think it spells doom for Scala.
- merb 11y agoI think most things he talked about are also fixed or deprecated. Collections are getting clearer and clearer.
- amock 11y agoMore than the specific problems with collections that he talks about, I think the problem of allowing clearly broken methods into the standard collections is the real issue. Why would they accept an implementation f map where map isn't safely composable? Why would they use incorrect type signatures? Why would they allow so many casts? I haven't finished the video yet but every issue he brings up seems to be about more than a mistake in a library. It looks to me like you can't trust Scala because the people behind it are ok with accepting clearly broken or poor quality implementations.
- adriaanm 11y agoYou don't have to trust us (though you can -- trust me :-)). Take a look at the source, check some references of happy Scala users. Submit a PR to fix what you don't like. Ask a question on our forums/stack overflow. Whatever you decide, I'd recommend rounding out your view of Scala by consulting more sources than Paul's rants. There's a lot of hyperbole there. This of course doesn't mean he's wrong, and we've certainly listened to him and fixed some of the issues he complained about (I was in the front row of that talk).