2 ms·
Scala the language is not the problem, as it is consistent and the rules aren't really complicated. However, the culture around the language and the libraries a
by bad_user 15y ago
Scala the language is not the problem, as it is consistent and the rules aren't really complicated. However, the culture around the language and the libraries are awful.
The problem with a language that has relaxed rules for syntax is that every complicated API ends up being a DSL. And you can do this with taste, or without taste.
Take SBT for instance. It is the standard build tool in Scala. SBT has many problems, the biggest one being that the chosen objective (type-safe DSL for project definitions) was the wrong problem to solve, with its second biggest problem being that it still relies on Maven. So instead of coming up with an alternative to the brokenness in Maven, the Scala folks that worked on SBT focused on only one of Maven's flaws (the XML config files, which were the least of everybody's problems).
And the DSL syntax in SBT is God-damn awful, with lines looking like this:
libraryDependencies <+= sbtVersion(
v => "com.github.siasia" %% "xsbt-web-plugin" % (v+"-0.2.10"))
The difference between this piece of shit and Ruby's Bundler is simply amazing. And newbies are exposed to this right from the beginning, as SBT is THE standard and as such every Scala library documents how to integrate with SBT ... in fact some libraries have such a dependency on SBT that integrating it with Maven or other build systems is a mystery (e.g. libraries that have a precompilation step).
So this is a language with a culture that (a) promotes cargo-culting through bad API design and (b) often breaks backwards compatibility.