News for hackers. Stuff that matters.
Re:Is Scala Really the Next C++? by simonw on Friday May 16, 2008 @02:47AM (#191532)
I think you missed the point of the comparison. One of the reasons C++ took off was that it was deliberately compatible with C (the dominant language at the time), so you didn't have to discard your existing C code and could ramp up from your existing skills. Likewise, today the dominant language is Java, and Scala compiles down to Java bytecode and allows you to continue to use your existing Java libraries. To my knowledge Erlang doesn't have these capabilities.
Re:Is Scala Really the Next C++? by KirinDave on Friday May 16, 2008 @10:47AM (#191823)
Erlang can integrate with anything out there, because it deliberately discourages binary inclusion. Instead you make remote "ports" that act like servers or vendors of results.

It's a very weird approach, but it's surprisingly effective.

Re:Is Scala Really the Next C++? by randomhack on Friday May 16, 2008 @11:35AM (#191860)
Well can you give more info about these ports? Sounds like you want to do interprocess communication of some kind with the JVM?

1. How exactly would you setup the JVM? Will you need to wrap every Java class you want to use with some kind of communication mechanism? What about callbacks?

2. Can you subclass a Java class?

3. What is the overhead of calling Java methods from Erlang?

4. Has anyone demonstrated a bridge to a non-trivial Java library using a language not running on the JVM?

I feel interprocess communication might be ok for some apps but not all apps.

Re:Is Scala Really the Next C++? by KirinDave on Friday May 16, 2008 @02:09PM (#192051)
1. Yes, you write a communication mechanism. You can either use an existing one (like Thrift) or use the Erlang binary protocol. Erlang expects you to be acting like an erlang message-based process, like an actor.

2. No. Erlang is not an OO langauge, although its concurrency model is the actor concurrency model, which sometimes feels like Smalltalk's object model.

3. The cost of communication. Having implemented a few systems that do this, I've found it to be fairly small, even using a slow glue layer like ruby. See https://github.com/KirinDave/fuzed/tree ... Powerset uses almost exactly this codebase to manage query analysis on its frontend before dispatching to our results retrieval layer. Thus far, it's been one of the most flexible and robust parts of our architecture.

I felt this way too, and it is the case in some very specific scenarios. But the truth of the matter is that Java itself is often the wrong tool in these cases, so it's somewhat of a red herring to say that.

4. http://erlang.org/documentation/doc-5.6.1/lib/jinterface-1.4...

Re:Is Scala Really the Next C++? by greyman on Friday May 16, 2008 @03:12AM (#191557)
Good comment. We can't only look at the merits of the language itself, but also see wider context and circumstances in the software world. Thus my answer to the original question is: No, it isn't.
Re:Is Scala Really the Next C++? by albertcardona on Friday May 16, 2008 @09:43AM (#191758)
Following the same argument, Clojure and Jython qualify just as well as Scala does.
Re:Is Scala Really the Next C++? by twism on Friday May 16, 2008 @10:13AM (#191785)
javascript using rhino as well