News for hackers. Stuff that matters.
Re:The JVM situation by adamnemecek on Tuesday June 18, 2013 @07:57PM (#5902826)
"Scala is not a well-designed language" regardless of anyone's opinion, that's a pretty ballsy thing to say on the scala DL :-).
Re:The JVM situation by PommeDeTerre on Tuesday June 18, 2013 @08:23PM (#5902915)
Members of the Scala community are generally quite mature, and this reflects in their attitude and response when it comes to legitimate criticism of Scala.

To most of these people, Scala is merely a tool, often just one among many others. They fully realize that it has flaws, and are very willing to acknowledge the existence of these flaws. They don't take it personally when somebody points out such problems. This is quite evident after reading through the discussion in this case.

This does differ from how members of the the Ruby and JavaScript communities take criticism of those languages, for example. Such people do tend to be much more emotionally attached to those programming languages, for whatever reason. They react with hostility and denial when they encounter legitimate criticism.

Technological improvement happens best when criticism can flow freely. The people involved are focused on acknowledging and accepting that flaws exist, and then proceed to try to fix them. On the other hand, when legitimate criticism is shunned or blindly denied, like in the JavaScript community, technological progress proceeds at a much slower pace. More effort is placed on defending and maintaining the status quo, even when this is the most ineffectual and non-beneficial thing to be doing, than is expended on improving the situation.

Re:The JVM situation by sanderjd on Tuesday June 18, 2013 @09:21PM (#5903174)
It's pretty simple really, and far from unique to programming (let alone to the Ruby and JS communities in particular): all communities tend to take criticism from insiders in good faith, and tend to take criticism from outsiders more personally. It is obvious from reading the thread that Tony Morris is "inside" the Scala community, both due to his demonstrated depth of knowledge and to the deference and consideration given to his question. You have to earn the ability to say "Scala is not well-designed" on a Scala list. If somebody showed up and started a thread saying, "I just discovered Scala and it is immediately clear to me that it is poorly designed", it would turn out very differently.

It seems to me that there is a pretty typical mix of criticism coming from inside the Ruby and JS communities being responded to thoughtfully, and criticism from outside being responded to defensively.

Re:The JVM situation by chii on Tuesday June 18, 2013 @10:46PM (#5903461)
why does one need to be "inside" the community and have gained reputation before making valid criticism?

If somebody who has never posted came out of the blue, and listed some criticisms (which are well researched and valid), it should be taken just as seriously as Tony Morris's piece.

Re:The JVM situation by sanderjd on Wednesday June 19, 2013 @11:01AM (#5905908)
I actually didn't say that one needs to be "inside" a community to criticize it, merely that all human communities tend to respond differently to criticism from within than from without. (For instance, Seinfeld's dentist Tim Wotley converting to Judaism "for the jokes".)
Re:The JVM situation by steveklabnik on Tuesday June 18, 2013 @08:40PM (#5902973)
> They react with hostility and denial when they encounter legitimate criticism.

Citation needed, Rubyists in particular have been whining (and rightfully so) about MRI's poor concurrency support for the past year or two. That's just one counterexample.

Everyone that I know that's good at Ruby has their own favorite wart where it does something they hate.

Re:The JVM situation by chimeracoder on Tuesday June 18, 2013 @09:12PM (#5903128)
> Citation needed, Rubyists in particular have been whining (and rightfully so) about MRI's poor concurrency support for the past year or two. That's just one counterexample.

To be fair, there's a huge difference between complaining about an implementation and complaining about the design of a language.

Re:The JVM situation by dragonwriter on Tuesday June 18, 2013 @10:59PM (#5903500)
> Citation needed, Rubyists in particular have been whining (and rightfully so) about MRI's poor concurrency support for the past year or two.

A lot longer than that, but, to be fair, that's a criticism of the main implementation, not the language -- and one of the selling points of JRuby. OTOH, there's been lots of criticism, and dissection, in the community of infelicities in the language design that make it difficult to implement efficiently.

Re:The JVM situation by azth on Wednesday June 19, 2013 @12:21AM (#5903731)
> This does differ from how members of the the Ruby and JavaScript communities take criticism of those languages, for example.

Don't forget Go. :)

Re:The JVM situation by octo_t on Tuesday June 18, 2013 @08:17PM (#5902890)
I think its recognised, even by people like Odersky, that the language has been significantly compromised by the decision to run on the JVM.

It is an incredibly well-designed language, but lots of that effort has gone into covering up some really nasty warts.

Re:The JVM situation by gruseom on Tuesday June 18, 2013 @09:08PM (#5903101)
I'd be interested to hear some examples of how the decision to run on the JVM has skewed the design of Scala. (Plus whether/how the same is true of Clojure.)
Re:The JVM situation by Aqueous on Tuesday June 18, 2013 @08:21PM (#5902904)
Here i am thinking it's the best language I've ever written in :-) I guess that's not really incompatible with still being "not a well designed language." When we're comparing ourselves to platonic ideals I guess the real thing can only pale in comparison. I just don't perceive the compromises.

For me, attaining a factor of 5 lines to 1 line code shrinkage translating from a legacy (though still imperative) codebase is amazing, and must point to an excellent language design. Of course I realize I could probably achieve the same thing with a number of other functional languages of which i have limited experience

Re:The JVM situation by octo_t on Tuesday June 18, 2013 @08:24PM (#5902918)
I absolutely agree (although for smaller projects I enjoy Haskell more).

Tony Morris (the person who started the conversation) is a pretty devoted Scala-er. But it is definitely recognised by Scala experts (especially people who are arms deep in the compiler) that the JVM is a very limiting factor in the design of the language.

Re:The JVM situation by michaelochurch on Tuesday June 18, 2013 @09:12PM (#5903127)
Scala is a great language to write in. It's also good because you can learn a lot about the JVM (that you wouldn't learn as easily in Clojure, because the JVM interop of Clojure is less mature and far less intuitive) but also about strong, static typing in a system almost as badass as Haskell's.

On the other hand, reading Scala code written by mediocre developers is painful. That's probably true of any language, but in Scala bad code comes with (a) minimal support from the IDEs that make shitty code navigable, (b) a less mature reflection API, and (c) serious compile-speed pains at scale. If anything kills Scala, it will be the the Java-in-Scala crowd-- the ones who failed to learn what Scala was really about and what it had to offer, but used it because their bosses demanded it.

Scala is well-designed-- extremely so, and almost no one here could have done better in that time-- in the context of its constraints (JVM) and purpose (a Haskell-like language on a VM with a top-down type system-- radically different from the bottom-up tying approach of traditional Hindley-Milner languages). Scala-bashing gets on my nerves for two reasons. First, if you understand the compromises that had to be made, it's hard to imagine it being done better. Second, you know what happens if Clojure and Scala developers beat each other up? Managers step in and make us write Java.

Re:The JVM situation by twic on Wednesday June 19, 2013 @02:32PM (#5907337)
And not only is it 5 lines to 1 line, the remaining 1 line is basically just underscores!
Re:The JVM situation by guard-of-terra on Wednesday June 19, 2013 @05:54AM (#5904655)
They would never get it out of the door if it wasn't based on the JVM. The reason is Haskell. JVM mandates certain imperative tools in the Scala language; if you subtract these, you end up with Haskell, and Haskell is big enough that you'll have hard time reinventing it.
Re:The JVM situation by jbrechtel on Wednesday June 19, 2013 @04:04PM (#5907827)
Let's just say that Tony Morris doesn't mince words on the Scala MLs.....