3 ms·

Odersky forcing through major syntax changes for Scala 3 was such an unforced error. It's baffling add new syntax on top of major semantic changes to the type s

by adamwk 2y ago

Odersky forcing through major syntax changes for Scala 3 was such an unforced error. It's baffling add new syntax on top of major semantic changes to the type system.

Pet_Ant 2y ago
But did it provide a gain in power and soundness? There issues with the 2.x system.
- merb 2y ago
  Most programming languages have unsound features.
- lmm 2y ago
  It did, which makes it all the more frustrating that you can't adopt it separately from the syntax and tooling changes.
  - Taikonerd 2y ago
    But the new syntax is optional, right? So you could upgrade and keep the old syntax? (I'm not a Scala dev, so this is just my impression.)
    - lmm 2y ago
      Some of the syntax changes are optional, some of them like the _/* change aren't.
hawk_ 2y ago
Stroustrup said "There's two kinds of PLs, ones that people complain about and ones that nobody uses." Odersky made Scala3 become a language that nobody uses and people complain about!
threeseed 2y ago
Problem is he’s a full time academic. So he doesn’t care if this amazing feature he’s invented has no IDE support. Or if the Scala tooling ecosystem is so ridiculously poor.