News for hackers. Stuff that matters.
Re:Scala 2.13 is now available by mrkeen on Tuesday June 11, 2019 @06:41AM (#20154282)
I'm doubling down on my "both worlds" point, whether you state it as (scala = FP and OO) or (scala = FP or OO).

My choice to be null-free does not survive my coworkers' choice to use null. Likewise with mutability, purity, inheritance etc.

The feature that I want is to look at (n : T) and understand that T is T, not (T | ? extends T) and that n is n, not (n | null), or n now and n' later.

Re:Scala 2.13 is now available by pas on Tuesday June 11, 2019 @07:27AM (#20154465)
It's not Scala's fault if a team can't decide on a coherent coding style/standard, but I feel your point :(

That's why Rust's safety first creed is so welcome. (And that there's --strict in TypeScript.)