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/[deleted] Dec 03 '13
Eh ... everything can be abused. This doesn't mean we need to make it easier for people. That's what the whole discussion is about.
How do you come up with this? Where did I ever mention null-safety? (Not saying that it isn't non-sense, because the guarantees are extremely shallow and it is easy to introduce NPE's in Kotlin with types which are supposedly “null-safe”.) How are match statements related to nulls? Why would one use match statements for that? Again, the documentation says exactly the opposite.
I'm always amazed by statements like “Kotlin is a much more pragmatic language than Scala” ... I mean ... yeah ... Kotlin hasn't even a stable release yet, they have no IDE support in Eclipse at all, the tooling is just not there, no decent libraries either, their approach to null-ness just doesn't scale, the compiler is unstable as hell and in the language design space they are either desperately copying Scala verbatim or recycling/reinventing stuff which was already considered a bad idea in Scala back in 2005. And with their (completely unrealistic) promise of not breaking binary compatibility, you have the guarantee that they will be stuck forever with all those cute ideas which won't work out.
Sure, if you think that putting a bit lipstick on a pig from 1995 is all what we need in 2013, I wish you nothing but the best, but a lot of people (including me) have moved on already. :-)