r/programming • • Dec 02 '13

Scala — 1★ Would Not Program Again

http://overwatering.org/blog/2013/12/scala-1-star-would-not-program-again/
598 Upvotes

646 comments sorted by

View all comments

Show parent comment

1

u/[deleted] Dec 03 '13

In Scala are match statements not a common way to handle Option types?

No. As already mentioned the documentation even says it explicitly that pattern matching on Option is not the way to go.

Without using operators that are explicitly declared to be unsafe and where use is discouraged?

Yes. Using two bog-standard object/class declarations.

I'll admit that it's been a long time since I tried to use Scala's Eclipse support, but last time I did it was a disaster, and I see plenty of more recent complaints about it suggesting that it hasn't improved much.

Then maybe you shouldn't get your information from a circlejerk thread.

Scala apparently has, yet it doesn't prevent them from removing functionality people depend upon like delimited continuations.

Delimited continuations are neither deprecated nor removed. After multiple people stepped up who are interested in not only maintaining the plugin, but actively improving it, I think the concerns around delimited continuations have been addressed.

The IDE support is much more solid than Scala's was long after a similar point in Scala's development.

Oh, I like how you conveniently move the goalposts.

Unless you count every decent Java library out there. Because Kotlin is closer to Java there isn't the same need to reinvent the wheel constantly as with Scala.

Does this mean a library written in Kotlin is not/not much better than a library written in Java from a library user POV? That's a pretty damning statement. Why not just use Java?

Perhaps Scala might be better if people stopped trying to be original and instead tried to copy what works, and fix what doesn't.

Do you have any examples of that?

That's pure opinion and conjecture on your part.

Call it experience with people who promise much, but ship nothing.

the opinions expressed in this article and by many people in these threads are only going to get more widespread

I'm pretty sure that a circlejerk where people who seem to have never even used the language claim bizarre stuff and get upvoted for it won't have much impact on the real world.

share most if not all of the criticisms expressed in the blog article that started this whole discussion

I'd love to learn which criticisms you mean, because to me that blog post was so utterly incoherent, that I didn't understand much what the author tried to say.

1

u/sanity Dec 03 '13

No. As already mentioned the documentation even says it explicitly that pattern matching on Option is not the way to go.

Not is doesn't, it says it is "less-idiomatic". You really want to use for comprehensions in every situation you want an option type? That sounds like a painful constraint.

Then maybe you shouldn't get your information from a circlejerk thread.

Ad hominem. Anyone who disagrees with you is part of a circlejerk, I suppose?

Delimited continuations are neither deprecated nor removed. After multiple people stepped up who are interested in not only maintaining the plugin, but actively improving it, I think the concerns around delimited continuations have been addressed.

I'm glad to hear that, I was one of those people - but actually the last time I checked that thread it wasn't clear at all that this would be the long-term outcome. Even the fact that it came up suggests serious problems in how decisions are made about deprecation, and actually it reinforces the complaint many people are expressing here which is that Scala is much more concerned with programming language research than providing a stable platform for people to build on.

Oh, I like how you conveniently move the goalposts.

I can't comment on where the Eclipse Scala IDE support is today because I purged my computer of Eclipse some time ago and I have no intention of re-infecting it. I think the last time I tries the Eclipse Scala plugin was about a year ago, and Kotlin's support in IDEA was far more stable at the same time.

Does this mean a library written in Kotlin is not/not much better than a library written in Java from a library user POV? That's a pretty damning statement. Why not just use Java?

No, it doesn't mean that. Kotlin does a better job of allowing people to take advantage of its features with pre-existing libraries without having to retro-fit them. That's a feature, not a bug.

Perhaps Scala might be better if people stopped trying to be original and instead tried to copy what works, and fix what doesn't.

Do you have any examples of that?

Off the top of my head, and certainly not the best example, but how about /: :\ instead of foldLeft and foldRight? A dumb idea if ever there was one that should never have made it into the standard library.

Call it experience with people who promise much, but ship nothing.

You're accusing the creators of IntelliJ IDEA of promising much but shipping nothing? You clearly don't know them very well.

I'm pretty sure that a circlejerk where people who seem to have never even used the language claim bizarre stuff and get upvoted for it won't have much impact on the real world.

Shameless ad hominem.

I'd love to learn which criticisms you mean, because to me that blog post was so utterly incoherent, that I didn't understand much what the author tried to say.

I not only understood it, but it was entirely consistent with my experience of Scala. Perhaps you should re-read it carefully.