4 ms·

Things haven't changed, using Scala doesn't offer significant benefits over Java and it is just a noisy minority that pontificate over Scala and its supposed (l

Things haven't changed, using Scala doesn't offer significant benefits over Java and it is just a noisy minority that pontificate over Scala and its supposed (largely academic) benefits. This is the thing I find most annoying regarding Scala use, and people advocating its use, it just doesn't do anything that Java can't do - plus the tooling for Java is wayyy better, there is a smaller learning curve, you can hire people to work with it and you don't spend your days endlessly debating what obscure language feature that may lead to tighter code in release 2.11.B.3.48d.M1.

trailfox 13y ago
> "Scala and its supposed (largely academic) benefits" Perhaps you would like to discuss the "academic" benefits with the likes of Twitter and Foursquare? > "it just doesn't do anything that Java can't do" It's a more expressive language. You could argue that Go and Python can't do anything that C or assembler can't do. That doesn't make Python irrelevant. > "plus the tooling for Java is wayyy better" In terms of the JVM the tooling is exactly the same. In terms of coding I use IntelliJ for both Scala and Java development, without noticing much difference in quality between the support for either language. In terms of libraries Scala has access to all the libraries that java has as well as additional libraries designed specifically for Scala. Most (actually all) Java developers that I know grumble when having to code in Java after they are exposed to Scala.
- edwinnathaniel 13y ago
  > Perhaps you would like to discuss the "academic" benefits with the likes of Twitter and Foursquare? Academic vs Practical probably? What's the point of discussing with <big-name-company>? Devs there do like to try out new tools, new languages, new platforms for the sake of trying as well. Devs are humans with ego as well, just like the rest of us. > Most (actually all) Java developers that I know grumble when having to code in Java after they are exposed to Scala. I code in Java, Python, JavaScript (modern) and playing with Ruby/Rails lately but I never grumble when I have to go back to Java because I know there are limitations/disadvantages of the other platforms as well. I use SVN and Git and I never grumble when I go back to SVN on a very large project with multiple component that have dependencies. Context is everything. YMMV.
johnx123-up 13y ago
I'm also in Java->Scala->Java boat. Supporters often say Scala codes are concise, but we can also write concise Java codes--by properly using 3rd party packages. Also, if you code using frameworks like Play!, there's no significant reduction of LOC (for Scala vs Java) Scala may be good for one-dev company; but terrible in terms of readability and maintenance for a team where more than 3 programmers work on the same code.
- pkolaczk 13y ago
  It is not mainly about conciseness. Conciseness by itself is not that important. Conciseness is a side-effect of being able to apply DRY and to build more powerful abstractions. You could write more concise Java by using one letter identifiers everywhere, but that would only make things worse, wouldn't it?
- seglo 13y ago
  Scala can work great in a large development team. Your sentiments about poor readability and maintenance have little to do with the technology itself; you could say this about any programming language. People new to a technology have a tendency to flounder around a bit in the beginning because they're naive to common coding standards and principles. After those are found or established then Scala codebases are just as easy to collaborate with on than any other.

trailfox 13y ago

> "Scala and its supposed (largely academic) benefits" Perhaps you would like to discuss the "academic" benefits with the likes of Twitter and Foursquare? > "it just doesn't do anything that Java can't do" It's a more expressive language. You could argue that Go and Python can't do anything that C or assembler can't do. That doesn't make Python irrelevant. > "plus the tooling for Java is wayyy better" In terms of the JVM the tooling is exactly the same. In terms of coding I use IntelliJ for both Scala and Java development, without noticing much difference in quality between the support for either language. In terms of libraries Scala has access to all the libraries that java has as well as additional libraries designed specifically for Scala. Most (actually all) Java developers that I know grumble when having to code in Java after they are exposed to Scala.

edwinnathaniel 13y ago
> Perhaps you would like to discuss the "academic" benefits with the likes of Twitter and Foursquare? Academic vs Practical probably? What's the point of discussing with <big-name-company>? Devs there do like to try out new tools, new languages, new platforms for the sake of trying as well. Devs are humans with ego as well, just like the rest of us. > Most (actually all) Java developers that I know grumble when having to code in Java after they are exposed to Scala. I code in Java, Python, JavaScript (modern) and playing with Ruby/Rails lately but I never grumble when I have to go back to Java because I know there are limitations/disadvantages of the other platforms as well. I use SVN and Git and I never grumble when I go back to SVN on a very large project with multiple component that have dependencies. Context is everything. YMMV.

johnx123-up 13y ago

I'm also in Java->Scala->Java boat. Supporters often say Scala codes are concise, but we can also write concise Java codes--by properly using 3rd party packages. Also, if you code using frameworks like Play!, there's no significant reduction of LOC (for Scala vs Java) Scala may be good for one-dev company; but terrible in terms of readability and maintenance for a team where more than 3 programmers work on the same code.

pkolaczk 13y ago
It is not mainly about conciseness. Conciseness by itself is not that important. Conciseness is a side-effect of being able to apply DRY and to build more powerful abstractions. You could write more concise Java by using one letter identifiers everywhere, but that would only make things worse, wouldn't it?
seglo 13y ago
Scala can work great in a large development team. Your sentiments about poor readability and maintenance have little to do with the technology itself; you could say this about any programming language. People new to a technology have a tendency to flounder around a bit in the beginning because they're naive to common coding standards and principles. After those are found or established then Scala codebases are just as easy to collaborate with on than any other.