4 ms·

My experience with Scala matches this pretty closely https://www.reddit.com/r/scala/comments/4246qc/heres_why_scala_sucks/ https://www.reddit.com/r/scala/commen

• lmm 8y ago
  That's a strange set of complaints for a clojure advocate, since most of what they're complaining about is not too much syntax but too little - no mandatory braces, mandatory brackets, mandatory types. Indeed "a -> b" for "(a, b)" is not syntax or even a macro, but just a function. _ is genuinely costly syntax, as are by-name parameters (though less costly in an age of IDEs). I consider _ to be worth its while (indeed I miss it a lot when writing lambdas in any other language); if you're going to have syntax in your language at all then it's one of the most general-purpose, effective constructs I've seen.
  • yogthos 8y ago
    The problem isn't whether there's too much or too little, it's that the syntax is incredibly inconsistent. There are a million ways to do anything, and you have to juggle it all in your head. Consider stuff like this: https://twitter.com/pembleton/status/1116343189437394944 https://twitter.com/pembleton/status/1116343189437394944 A new line can be significant syntax in Scala! With s-expressions, all of this mental overhead goes out of the window. I have regular boring syntax where pretty much everything works the same way. It's incredibly liberating. On top of that, s-expression syntax facilitates structural editing, where I'm manipulating the code tree semantically as opposed to thinking about moving lines of text around.