Why doesn't Sun do a C# to Java byte code compiler? -


We want to run our C # code on JVM

One of my company's big # Code Base is more than half of this code, our main engine for creating, reading, modifying, computing and writing Excel workbooks. We often ask customers and potential customers questions whether we are going to build a Java version of our engine - many of them are not interested in UI. We also have some customers who have had trouble using our .NET Library from our Java applications.

Therefore, we want to build a Java version of our original engine, ideally without maintaining a separate Java source code base.

Eric Sink is very well I am in the same position except for the fact that our software license includes royalty free deployment, Eric has to choose for us a nonstiter.

I've been googling for many years for several years, having spent some ~ 7 years developing similar software for Java, I have full confidence that we use it in our original engine. The API can be easily explained and we can fulfill all the needs of using the Java Library. Therefore, if we had C # -> JVM Compiler then we could build our main engine for Java and now we have to shut down Java developers who want to use it.

I'm not asking for this for technical reasons why the Sun does not have a C # compiler. I understand that Java does not have any properties or an unsigned 64 bit long, etc. ... logic For, just assume that these technical issues can be extended to Jammu and / or other methods.

And I'm not saying for another debate why a language / stack might be better than the other. The reality in our business is that every potential customer can be used in it.

Why should Sun be a C # compiler? (Of the IMO course)

Simplifying the C # code on the Java platform means more software for developers and platforms. Is anything more important for the success of a platform? A software man, I will make it more clever than others, whether it is on impossible work as chairman and chief of the sun, but after joining with Sunt some time after joining with Jonathan, it is that the software Understands and the base of big developers

So why do the Sun do a C # compiler?

  1. Syndrome?
  2. The ghost?
  3. Do many Java developers dislike any dislikes or distrust related to Microsoft?
  4. Do not agree as part of taking it?
  5. ???

There should be a good reason I can not just understand what it is for my life ...

First of all, zero non-encouragement to implement C # compiler on JVM because they have something similar to Java programming language

It is also not really simple that just Java standard class libraries Implement a compiler as a pure original square Is not the same as Tkalyon. You can change all .NET API calls for Java API calls.

The Microsoft product was called J # which was for NAT conversion for Java, but in the end no one has used it because the API was limited to the former Java 2 API so it was mostly useless . It would be similar if some parts of the NAT BCL were implemented by the Sun, because only the main sections are standard and royalty free. Parts such as ASP.NET and WPF, WCF etc. are not part of the ECMA standards and therefore the sun will require the permission of Microsoft to implement those APIs.

If enough clients want a Java version to do this commercially to shut down your application in Java, then any help from the Sun is possible through any C # to the JVM Compiler. Will not receive.


Comments