EDN Admin
Well-known member
Hi heveryone, forgive my naivete as Im new to studying the C#/.Net world. Ive just begun reading Troelsens
<span style="text-decoration:underline Pro C# 2010 and the .Net Platform and on page 5 under Life as a Java Programmer he states:
"Although Java is a very elegant language, one potential problem is that using Java typically means that you must use Java fron to back during the development cycle. In effect, Java offers little hope of language integration, as this goes against the grain
of Javas primary goal -- a single programming language for every need. In reality, however, there are millions of lines of existing code out there in the world that would ideally like to commingle with newer Java code. Sadly, Java makes this task problematic.
While Java does provide a limited ability to access non-Java APIs, there is little support for true cross-language integration."
I am confused by his assertion because today we witness JRuby, Clojure, Scala and so on. Can one of you perhaps help me understand what Troelsen is asserting here, and how .Net differs from Java in this manner? I realize that .Net offers "interoperability
with existing code" such as existing COM binaries and "support for numerous programming languages" such as C#, VB, F#, and so on. But how is this different from Javas support of different languages? Doesnt this conflict with what Troelsen asserts?
Thanks for your insight.
View the full article
<span style="text-decoration:underline Pro C# 2010 and the .Net Platform and on page 5 under Life as a Java Programmer he states:
"Although Java is a very elegant language, one potential problem is that using Java typically means that you must use Java fron to back during the development cycle. In effect, Java offers little hope of language integration, as this goes against the grain
of Javas primary goal -- a single programming language for every need. In reality, however, there are millions of lines of existing code out there in the world that would ideally like to commingle with newer Java code. Sadly, Java makes this task problematic.
While Java does provide a limited ability to access non-Java APIs, there is little support for true cross-language integration."
I am confused by his assertion because today we witness JRuby, Clojure, Scala and so on. Can one of you perhaps help me understand what Troelsen is asserting here, and how .Net differs from Java in this manner? I realize that .Net offers "interoperability
with existing code" such as existing COM binaries and "support for numerous programming languages" such as C#, VB, F#, and so on. But how is this different from Javas support of different languages? Doesnt this conflict with what Troelsen asserts?
Thanks for your insight.
View the full article