It really works very fast! It is like SWING, but uses OS's native GUI. Mac OSX version is just released. Also, you can use Eclipse open source IDE, which is available on all the platforms, and the best IDE that you can find around. It supports refactorings, and has a terrific plug-in structure. There are 100s of plug-ins ready to be used already.
Check out : www.eclipse.org
My two fathers and I are having orgies every night! It should be hard for your mom, but she looks like she is able to handle three cocks. Lucky boy! ; )
Hahahahaha! Perfect! Really thanks for that!:) But don't forget that people with two heads do not live much. You know.:) It is not multiple inheritance, but selective one.
MI, Operator Overloading and Pointers mustn't be added to the Java. -MI does not exist in nature. It is cheating to abstract some entities in an easier way. It simply does not work except for several cases. -You can do everything you can do with Operator Overloading without using Operator Overloading. It certainly helps to reduce the syntax complexity of numerical applications, but, generally easy to abuse, or misuse by creating wrong semantical correlations. There are many cases, in which the "addition" operator for some entity may be defined with more than one semantics. In big projects, it leads to confusion, and hard to determine bugs. I had a problem with them, I know. Much better to not to have it. -Once pointers enter into a language, expect memory leaks, dangling pointer bugs etc. By the way, on virtual machine based systems, you cannot implement dynamic languages, which contains pointers, and memory access.
All the big firms other than MS have J2EE based servers. Such as: Sun, IBM, Apple, HP, Fujitsu, BEA, Oracle, Sybase. Oh, there are also open source choices: JBoss, OpenEJB.
Can you show me one.NET server? MS released last week after one year lag "nearly-finished" version of their.NET server.
.NET is very fast on Windows. So what? For example, unmanaged code calling is not fast enough, although it does not have JNI like layer. My firm tried to call some C++ functions and Active X controls to test.NET, they abandoned it immediately after huuuuge performance hit. Also, do you guys understand that cross-platform-compatibility is important especially in the last 2 years?.NET will never be cross-platform-compatible. Sun has not released control of it to anyone. So what? Did MS released all parts of.NET? They did not release the most important part: Enterprise Services Framework. Say goodby to.NET transactions in Mono. I am seriously seing every firm here is trying to getting rid of Windows, and moving to Java. I think the recent increase in Java projects and interest in Java programmers proves my claim.
Why I think that they will not? Because Miguel de Icaza changed his mind and said Mono will not implement WinForms. I don't know if he changed his mind again. He looks like changing his mind every now and then. There was a discussion about it last week or the previous week here at/., Icaza himself said he changed his mind, and will not implement WinForms. I would spot it if I had time. Please look for it for yourself.
Well, using a system is something, trusting a system is another. J2EE is around for how many years? Its is now mature, after all these years. IBM's application server reached version 6 or something. After Mono's release, I would not dare to use it for couple of years. If it is gonna be used in serious project, it has to get mature and prove itself, which takes years.
Please get a life..NET will never be cross platform. MS would never let it. AND, WHY should I wait anyway? JAVA is working RIGHT NOW, and it is already MATURE, and it already PROVED ITSELF, and it is already CROSS PLATFORM COMPATIBLE, and there are many J2EE servers (open/closed source), web services implementations (open/closed source), thousands of ready to use libraries, frameworks, projects (open/closed source) to chose from:
http://www.javaskyline.com/webservices/
http://www.javaskyline.com/serv.html
Can you show me a.NET server available on the market? Just show me one. Even MS released "nearly finished" version of its.NET server AFTER ONE YEAR LAG. Forget about being robust, and mature, it is not even finished yet! After its release, minimum 3 years for bug fixing and adoption.
Do you recognize that ALL the big firms of the IT market already rolled their dice, and chosen Java for their application servers? For example, Sun, Oracle, Sybase, IBM, HP, Macromedia, BEA, JBoss, OpenEJB. ALL of them are based on J2EE. All of them are mature, proved themselves after years of improvements.
Well, I believe,.NET will be used extensively on Windows platform. On Linux, probably for couple of client side applications.
Which is taken directly from Sun's framework, and improved it just a bit..NET's language independence is a bit exagerated. It is not possible to create a VM which would be able to hold all different kinds of languages. It simply does not make sense, since there are many different type of languages..NET languages are not the real languages. They are crippled and extended versions to fit into CLR.
I personally don't see anything beautiful in.NET. Sun's way is much better. By the way, there are Java 3 gossips around. Beware the Gosling's new attack. Remember, he designed Java 10 years ago.:)
Mono, actually, do not interest me a gram because of the following reasons: - MS already started.NET 2. Mono will always come with a minimum 2 years lag behind original.NET. - MS did not give everything about.NET to Ecma. ADO.NET, Winforms, and maybe the most important, Enterprise Services framework (which contains very important parts, such as transactions.) are not given to the Ecma for instance. Since MS holds the patents, it is not possible for Mono or any other.NET implementation to implement them. Mono already step back from its previous claim and said they will not implement Winforms etc. So,.NET will never be cross platform. Tweaking? Oh, please don't make me laugh. - What estonishing speed are you talking about????.NET is there for more than 2 years. Mono is there for 1.5 years, still no release. After the release, nobody will trust it at least until it proves itself. MS even have problems with it..NET, even on Windows platforms is not moving fastly. Lately Billy_the_McCarty said.NET needs 4 years to mature. Java is already mature, and it is already cross platform. - What I am seing is, everybody is moving to Java. Why should I wait for.NET? Why should I care about Mono? Everything it promisses is already available with Java NOW. Which is mature and cross platform already.
Do you know anything about Java 2D? Java 3D? What you Anti-Java people know is "Java is slow." When did you last visited Sun's site and learned about the latest improvements in JIT compilers etc? Do you have a Zaurus and tested Java on Zaurus? Stop showing degree of your idiocy and spreading Java FUD. Idiot.
Maybe you should do it yourself. Just last week Miguel said they CHANGED their mind, and will not support WinForms with Mono, HERE ON SLASHDOT.
Do you understand that they cannot implement WinForms, ADO.NET, or EnterpriseServices.namespace (the one containing transactions etc.), since MS is holding patterns to these most important parts of.NET?
Maybe you should check it out. ; ) One language is always an advantage. If every computer engineer knew only one language (of course ONE for ONE language type. Such as LISP and C++ are different, used for different things.) everything would be much easier.
Also, CLI is just another VM like JVM. It is possible to develop more than one languages over JVM too. There are something like 160 languages already developed on top of JVM. But, Sun did not want to push these. It only concentrated on Java, since they knew about the power of being equilingual. MS also knows that, so that C# is the most prominent language of.NET. That is why they did not give VB.NET etc. the same broad functionality as C#. Different languages of.NET is a marketing bullshit. Check out JVM languages here: http://grunge.cs.tu-berlin.de/~tolk/vmlanguages.ht ml
The important thing is it is not possible to create a VM, which may support all the languages. Because there are huge variety of languages. For instance, it is not possible to run dynamic languages like C, C++ on top of VMs directly..NET VM is not an exception..NET has only one very generic language called CL (common language). All the.NET languages are the same language with same functionality and capability, with different syntatic sugar. So, in order to fit into CL, these languages are cut and crippled and changed to make them.NET compatible. I am sorry, but that is not my type of thing.
We have no problems with Swing. Its working quite well. But if you do not like it, then use other GUI package, such as SWT from IBM (check out www.eclipse.org). It uses native widgets, and lightning fast.
The focus related issues were really mind boggling, I am very happy to see that they are solved in the end with 1.4 release. JDK 1.4.1b is a wonder, even in its beta stage. It is incredibly faster than the previous releases. But I am much more interested in JDK1.4.2, since it will contain new garbage collection features which is said improve performance incredibly. Well, we will wait and see.:)
Dear Anonymous Coward, MS cannot even approach J2ME's success. There will be 100 million Java phones in the world end of this year. What are you talking about?
Lets look at the application server world. BEA, ORACLE, IBM, SUN, HP, FUJITSU, JBOSS, ORION, APACHE, etc. All of their application servers, ALL of them, are Java J2EE based. It took years of these firms to mature these products. Make them secure, make them optimized. Websphere is in its 8th release or something like that. How many.NET based application servers are around?
Java is very very portable. It simply works. I am not lying. I've been developing in Java for 7 years. We have developed many products which DO work CURRENTLY on Mac, Mac OS, Windows 9x, NT, XP, 2000 etc, Linux, Unix, Solaris. The tweaking was necessary, as you said. 1 day tweaking for every new system. : )
C# has some superiorities over Java, but it is not important, since Java is working already. And, the improvements are not really vitally important. Apart from that, I do not like C# much, (I've been using it for one year), since I think that the additions over the Java language it brings are harmful. Such as operator overloading.
Also we should remember that neither C#, or Java are fixed languages. Java is getting better with every release. JDK 1.4.1b is working incredibly fast already. Has lots of new features.:)
Actually they sent all of it, then took it back, since they recognized what MS was doing. The point is, you can use Java language in a free manner. They language itself is in the control of the Sun (well, actually, not totally, through the JCP many other firms are controlling it.) Sun did never threaten open source community, or sees it as a virus, or communist. They are getting ready to release their own Linux distribution. Sun is protecting Java by holding its controls. Actually, they are doing really well. The only bad thing is that Sun's marketing do not work well enough, like MS's. Also, their JVM implementations could be better.
MS is much more unethical than Enron, or Worldcom.
-]The fact that Sun's current JDK does not support the tail recursion does not mean that the next releases will not support it. It just does not mandate with a reason. There are problems with supporting tail recursion optimization technique on virtual machine platforms. Also on.NET. I can't remember the details though. But, the open source JVM called Kawa supports tail recursive optimizations with some technique as far as I remember. But you are taking the subject too deep!:) These are not important at all:
-]I am not afraid of Mono. What I do not like is that Mono will help MS in couple of ways. I do not like MS. I find them extremely unethical. They are bullying bastards. I hate them.
-]You may think that Mono will reach production quality in a year, but I won't trust mono before 3 years. None of the decision makers would, until it proves itself after couple of years.
-] You are pulling the conversation into very low level details such as tail recursion optimization,.NET being Turing compatible etc. Those are not important. I used.NET and Java. I know both of them well. The point is there is no immediate advantage of using.NET over Java. The performances are not radically different in the end. Java is working already on many platforms. From technical point of view.NET can be interesting, but in real life, it is just another VM specification, and it is a newbee in the kingdom of Java which has been there for 7 years. It is mature, supported by millions of programmers, thousands of open/closed source projects, libraries, frameworks.
""you use "harmful" as a synomnym for "I don't understand it, therefore I am scared of it"."" It is not nice to make up things about someone that you don't know. I know C++ (I am using it for 9 years.), and Java (7 years) and C# (1 year) quite well. I don't like C++, because it is very powerful. There is too many responsibility on the shoulders of programmers. I saw lots of C++ projects full of pointer errors from C++ gurus. I saw incredibly hard to determine bugs related with wrong usage of operation overloading etc.
CLR can run unmanaged C++ code after turning it to managed CL code. The performance hit is incredible, I know, because I tried it. If you bypass translation, your C++ code might not be compatible with the platform you are running CLR. In both the cases, the point is running a dynamic language such as C++ on top of VMs do not make sense. You can also compile C++ code into JVM bytecode if you want to. But why? For what reason? I don't know.:)
1. Some JVMs support tail recursive based optimizations. Please read before you post:
http://www-106.ibm.com/developerworks/java/library/j-diag8.html
2. And what about.NET languages?.NET has only one language, and it is called CL (common language). All the other languages are on top of that. In other words, all.NET languages are essentially the same language with a different syntatic sugar. I played with.NET enough. Believe me I know it very well. MS also knows that more than one language is not something nice, so that they are pushing forward C#. If they wanted, they could give VB.NET etc same functionality, but they did not. What they want is to shift VB programmers to VB.NET, then to C#. Multiple language support is nothing but a marketing trick. Do you know the story of "Tower of Babylon?". I can invent a language and put on top of CLI. So what? Languages, number of languages etc. are not important at all.
Stop calling Mono a universal VM. It is not even completed on Linux yet. It will take 3 years to become robust afterwards. MS and Java will leap miles ahead during this time. In the end, Mono is not %100.NET compatible. Period.
C++ on.NET is not C++. You cannot create dynamic languages on top of virtual machine based environments. Also, my company tried calling C++ unmanaged legacy code and some Active X components from.NET, and of course rejected it after huuuuge performance hit.:P
And, I personally think that C++ is not such a nice language. I even think that many of the additions C# brought on top of Java are harmful.
If you like it, use.NET. I don't, and seems like the others also don't.
Slashdot Mirror
To keep while programming. I was very pleased with the previous version.
SWT is from IBM. Try it. It is really fast GUI framework for Java, it is cross platform, and it really rocks! www.eclipse.org
It really works very fast! It is like SWING, but uses OS's native GUI. Mac OSX version is just released. Also, you can use Eclipse open source IDE, which is available on all the platforms, and the best IDE that you can find around. It supports refactorings, and has a terrific plug-in structure. There are 100s of plug-ins ready to be used already. Check out : www.eclipse.org
By posting such unrelated and stupid message to this topic.\n
trg
http://www.thinkfree.com/
nt
My two fathers and I are having orgies every night! It should be hard for your mom, but she looks like she is able to handle three cocks. Lucky boy! ; )
Hahahahaha! Perfect! Really thanks for that! :) :)
But don't forget that people with two heads do not live much. You know.
It is not multiple inheritance, but selective one.
MI, Operator Overloading and Pointers mustn't be added to the Java.
-MI does not exist in nature. It is cheating to abstract some entities in an easier way. It simply does not work except for several cases.
-You can do everything you can do with Operator Overloading without using Operator Overloading. It certainly helps to reduce the syntax complexity of numerical applications, but, generally easy to abuse, or misuse by creating wrong semantical correlations. There are many cases, in which the "addition" operator for some entity may be defined with more than one semantics. In big projects, it leads to confusion, and hard to determine bugs. I had a problem with them, I know. Much better to not to have it.
-Once pointers enter into a language, expect memory leaks, dangling pointer bugs etc. By the way, on virtual machine based systems, you cannot implement dynamic languages, which contains pointers, and memory access.
I am happy to see someone else has this logical view! :)
JVM is the most important. It must run beautifully!
Why Sun's way is better?
.NET server? MS released last week after one year lag "nearly-finished" version of their .NET server.
Check out the following to see the options:
http://www.javaskyline.com/serv.html
http://www.javaskyline.com/webservices/
All the big firms other than MS have J2EE based servers. Such as: Sun, IBM, Apple, HP, Fujitsu, BEA, Oracle, Sybase. Oh, there are also open source choices: JBoss, OpenEJB.
Can you show me one
.NET is very fast on Windows. So what? For example, unmanaged code calling is not fast enough, although it does not have JNI like layer. My firm tried to call some C++ functions and Active X controls to test .NET, they abandoned it immediately after huuuuge performance hit. .NET will never be cross-platform-compatible. .NET? They did not release the most important part: Enterprise Services Framework. Say goodby to .NET transactions in Mono.
Also, do you guys understand that cross-platform-compatibility is important especially in the last 2 years?
Sun has not released control of it to anyone. So what? Did MS released all parts of
I am seriously seing every firm here is trying to getting rid of Windows, and moving to Java. I think the recent increase in Java projects and interest in Java programmers proves my claim.
Why I think that they will not? Because Miguel de Icaza changed his mind and said Mono will not implement WinForms. I don't know if he changed his mind again. He looks like changing his mind every now and then. There was a discussion about it last week or the previous week here at /., Icaza himself said he changed his mind, and will not implement WinForms. I would spot it if I had time. Please look for it for yourself.
Well, using a system is something, trusting a system is another. J2EE is around for how many years? Its is now mature, after all these years. IBM's application server reached version 6 or something. After Mono's release, I would not dare to use it for couple of years. If it is gonna be used in serious project, it has to get mature and prove itself, which takes years.
Please get a life. .NET will never be cross platform. MS would never let it. AND, WHY should I wait anyway? JAVA is working RIGHT NOW, and it is already MATURE, and it already PROVED ITSELF, and it is already CROSS PLATFORM COMPATIBLE, and there are many J2EE servers (open/closed source), web services implementations (open/closed source), thousands of ready to use libraries, frameworks, projects (open/closed source) to chose from:
http://www.javaskyline.com/webservices/
http://www.javaskyline.com/serv.html
Can you show me a .NET server available on the market? Just show me one. Even MS released "nearly finished" version of its .NET server AFTER ONE YEAR LAG. Forget about being robust, and mature, it is not even finished yet! After its release, minimum 3 years for bug fixing and adoption.
Do you recognize that ALL the big firms of the IT market already rolled their dice, and chosen Java for their application servers? For example, Sun, Oracle, Sybase, IBM, HP, Macromedia, BEA, JBoss, OpenEJB. ALL of them are based on J2EE. All of them are mature, proved themselves after years of improvements.
Well, I believe, .NET will be used extensively on Windows platform. On Linux, probably for couple of client side applications.
Which is taken directly from Sun's framework, and improved it just a bit. .NET's language independence is a bit exagerated. It is not possible to create a VM which would be able to hold all different kinds of languages. It simply does not make sense, since there are many different type of languages. .NET languages are not the real languages. They are crippled and extended versions to fit into CLR.
.NET. Sun's way is much better. By the way, there are Java 3 gossips around. Beware the Gosling's new attack. Remember, he designed Java 10 years ago. :)
.NET 2. Mono will always come with a minimum 2 years lag behind original .NET. .NET to Ecma. ADO.NET, Winforms, and maybe the most important, Enterprise Services framework (which contains very important parts, such as transactions.) are not given to the Ecma for instance. Since MS holds the patents, it is not possible for Mono or any other .NET implementation to implement them. Mono already step back from its previous claim and said they will not implement Winforms etc. So, .NET will never be cross platform. Tweaking? Oh, please don't make me laugh. .NET is there for more than 2 years. Mono is there for 1.5 years, still no release. After the release, nobody will trust it at least until it proves itself. MS even have problems with it. .NET, even on Windows platforms is not moving fastly. Lately Billy_the_McCarty said .NET needs 4 years to mature. Java is already mature, and it is already cross platform. .NET? Why should I care about Mono? Everything it promisses is already available with Java NOW. Which is mature and cross platform already.
I personally don't see anything beautiful in
Mono, actually, do not interest me a gram because of the following reasons:
- MS already started
- MS did not give everything about
- What estonishing speed are you talking about????
- What I am seing is, everybody is moving to Java. Why should I wait for
Do you know anything about Java 2D? Java 3D?
What you Anti-Java people know is "Java is slow."
When did you last visited Sun's site and learned about the latest improvements in JIT compilers etc?
Do you have a Zaurus and tested Java on Zaurus?
Stop showing degree of your idiocy and spreading Java FUD.
Idiot.
Maybe you should do it yourself. Just last week Miguel said they CHANGED their mind, and will not support WinForms with Mono, HERE ON SLASHDOT.
.NET?
:)
Do you understand that they cannot implement WinForms, ADO.NET, or EnterpriseServices.namespace (the one containing transactions etc.), since MS is holding patterns to these most important parts of
Well, wait and see then.
Maybe you should check it out. ; ) One language is always an advantage. If every computer engineer knew only one language (of course ONE for ONE language type. Such as LISP and C++ are different, used for different things.) everything would be much easier.
.NET. That is why they did not give VB.NET etc. the same broad functionality as C#. Different languages of .NET is a marketing bullshit. Check out JVM languages here: t ml
.NET VM is not an exception. .NET has only one very generic language called CL (common language). All the .NET languages are the same language with same functionality and capability, with different syntatic sugar. So, in order to fit into CL, these languages are cut and crippled and changed to make them .NET compatible. I am sorry, but that is not my type of thing.
Also, CLI is just another VM like JVM. It is possible to develop more than one languages over JVM too. There are something like 160 languages already developed on top of JVM. But, Sun did not want to push these. It only concentrated on Java, since they knew about the power of being equilingual. MS also knows that, so that C# is the most prominent language of
http://grunge.cs.tu-berlin.de/~tolk/vmlanguages.h
The important thing is it is not possible to create a VM, which may support all the languages. Because there are huge variety of languages. For instance, it is not possible to run dynamic languages like C, C++ on top of VMs directly.
We have no problems with Swing. Its working quite well. But if you do not like it, then use other GUI package, such as SWT from IBM (check out www.eclipse.org). It uses native widgets, and lightning fast.
:)
The focus related issues were really mind boggling, I am very happy to see that they are solved in the end with 1.4 release. JDK 1.4.1b is a wonder, even in its beta stage. It is incredibly faster than the previous releases. But I am much more interested in JDK1.4.2, since it will contain new garbage collection features which is said improve performance incredibly. Well, we will wait and see.
Cheers!
Dear Anonymous Coward, MS cannot even approach J2ME's success. There will be 100 million Java phones in the world end of this year. What are you talking about?
.NET based application servers are around?
:)
Lets look at the application server world. BEA, ORACLE, IBM, SUN, HP, FUJITSU, JBOSS, ORION, APACHE, etc. All of their application servers, ALL of them, are Java J2EE based. It took years of these firms to mature these products. Make them secure, make them optimized. Websphere is in its 8th release or something like that. How many
Java is very very portable. It simply works. I am not lying. I've been developing in Java for 7 years. We have developed many products which DO work CURRENTLY on Mac, Mac OS, Windows 9x, NT, XP, 2000 etc, Linux, Unix, Solaris. The tweaking was necessary, as you said. 1 day tweaking for every new system. : )
C# has some superiorities over Java, but it is not important, since Java is working already. And, the improvements are not really vitally important. Apart from that, I do not like C# much, (I've been using it for one year), since I think that the additions over the Java language it brings are harmful. Such as operator overloading.
Also we should remember that neither C#, or Java are fixed languages. Java is getting better with every release. JDK 1.4.1b is working incredibly fast already. Has lots of new features.
Actually they sent all of it, then took it back, since they recognized what MS was doing. The point is, you can use Java language in a free manner. They language itself is in the control of the Sun (well, actually, not totally, through the JCP many other firms are controlling it.) Sun did never threaten open source community, or sees it as a virus, or communist. They are getting ready to release their own Linux distribution. Sun is protecting Java by holding its controls. Actually, they are doing really well. The only bad thing is that Sun's marketing do not work well enough, like MS's. Also, their JVM implementations could be better.
MS is much more unethical than Enron, or Worldcom.
-]The fact that Sun's current JDK does not support the tail recursion does not mean that the next releases will not support it. It just does not mandate with a reason. There are problems with supporting tail recursion optimization technique on virtual machine platforms. Also on .NET. I can't remember the details though. But, the open source JVM called Kawa supports tail recursive optimizations with some technique as far as I remember. But you are taking the subject too deep! :) These are not important at all:
.NET being Turing compatible etc. Those are not important. I used .NET and Java. I know both of them well. The point is there is no immediate advantage of using .NET over Java. The performances are not radically different in the end. Java is working already on many platforms. From technical point of view .NET can be interesting, but in real life, it is just another VM specification, and it is a newbee in the kingdom of Java which has been there for 7 years. It is mature, supported by millions of programmers, thousands of open/closed source projects, libraries, frameworks.
-]I am not afraid of Mono. What I do not like is that Mono will help MS in couple of ways. I do not like MS. I find them extremely unethical. They are bullying bastards. I hate them.
-]You may think that Mono will reach production quality in a year, but I won't trust mono before 3 years. None of the decision makers would, until it proves itself after couple of years.
-] You are pulling the conversation into very low level details such as tail recursion optimization,
No, I did not try to deflect debate.
:)
""you use "harmful" as a synomnym for "I don't understand it, therefore I am scared of it".""
It is not nice to make up things about someone that you don't know. I know C++ (I am using it for 9 years.), and Java (7 years) and C# (1 year) quite well. I don't like C++, because it is very powerful. There is too many responsibility on the shoulders of programmers. I saw lots of C++ projects full of pointer errors from C++ gurus. I saw incredibly hard to determine bugs related with wrong usage of operation overloading etc.
CLR can run unmanaged C++ code after turning it to managed CL code. The performance hit is incredible, I know, because I tried it. If you bypass translation, your C++ code might not be compatible with the platform you are running CLR. In both the cases, the point is running a dynamic language such as C++ on top of VMs do not make sense. You can also compile C++ code into JVM bytecode if you want to. But why? For what reason? I don't know.
1. Some JVMs support tail recursive based optimizations. Please read before you post: http://www-106.ibm.com/developerworks/java/library /j-diag8.html
.NET languages? .NET has only one language, and it is called CL (common language). All the other languages are on top of that. In other words, all .NET languages are essentially the same language with a different syntatic sugar. I played with .NET enough. Believe me I know it very well. MS also knows that more than one language is not something nice, so that they are pushing forward C#. If they wanted, they could give VB.NET etc same functionality, but they did not. What they want is to shift VB programmers to VB.NET, then to C#. Multiple language support is nothing but a marketing trick. Do you know the story of "Tower of Babylon?". I can invent a language and put on top of CLI. So what? Languages, number of languages etc. are not important at all.
.NET compatible. Period.
2. And what about
Stop calling Mono a universal VM. It is not even completed on Linux yet. It will take 3 years to become robust afterwards. MS and Java will leap miles ahead during this time. In the end, Mono is not %100
C++ on .NET is not C++. You cannot create dynamic languages on top of virtual machine based environments. Also, my company tried calling C++ unmanaged legacy code and some Active X components from .NET, and of course rejected it after huuuuge performance hit. :P
.NET. I don't, and seems like the others also don't.
And, I personally think that C++ is not such a nice language. I even think that many of the additions C# brought on top of Java are harmful.
If you like it, use