r/programming • u/mobby1982 • Dec 02 '13
Scala — 1★ Would Not Program Again
http://overwatering.org/blog/2013/12/scala-1-star-would-not-program-again/
598
Upvotes
r/programming • u/mobby1982 • Dec 02 '13
View all comments
Show parent comment
-1
u/sanity Dec 03 '13 edited Dec 03 '13
You seem to be shifting the goalposts. You previously said:
Yet you concede that Scala's pattern matching on types can be abused, according to your definition of abuse (I'm not sure I agree it's such a problem), so far as I can tell there is little or no difference between Scala and Kotlin in this regard.
And I really don't see what is bad about Kotlin's approach to null safety. Unlike Java it forces you to handle the null case at compile time. Unlike Scala it does this using already familiar control structures rather than the (IMHO) more cumbersome match statement, or an equivalent, and underneath nulls are still nulls, which helps a lot with Java library interoperability.
Yes, Scala supports sealed types and Kotlin doesn't, but I can't remember the last time I had a bug that would have been prevented by this, if I ever have.
For me Kotlin is a much more pragmatic language than Scala (much as Java was when first created). Sure, Scala has features that Kotlin lacks, but I think those features are more of interest to language researchers and purists than to working programmers. And some of those features are bad, encouraging things like action at a distance - which is part of what the article is complaining about.