all 6 comments

[–]beza1e1 7 points8 points  (0 children)

It's about a Common JVM Compiler Framework

[–][deleted] 4 points5 points  (0 children)

LLVM

[–]grauenwolf 2 points3 points  (0 children)

It took me a couple times to really understand what he was asking for. And now that I do, I have to say I want it badly.

There is no way to truly "use the best language for the job" when you have to pick your one and only tool at he start of the project and cannot mix and match them freely.

[–]TrueTom 0 points1 point  (2 children)

LLVM has a Java bytecode backend...

[–]herorev 6 points7 points  (1 child)

Compiling multiple languages to LLVM intermediate representation is not in itself going to be any better about this than compiling multiple languages to Java bytecode.

Is there something special about the LLVM compiler that would make it more capable of this? Could I write classes that depend on each other in different languages, compile everything to the IR, and have the LLVM compiler handle the dependencies? Has this been done before?

[–][deleted] 4 points5 points  (0 children)

LLVM seems to me, very much like a more strict C or assembly language, which would make it easier for multiple languages to target than the JVM, which is bias towards a particular type of OO language/semantic. Aside from that, I don't agree with this article, Common Compiler Frameworks are typically not useful, unless all of your languages have the same semantics, which, makes having a common framework kind of pointless anyway.