File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Java in General and the fly likes Is J# really the future? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Java in General
Bookmark "Is J# really the future?" Watch "Is J# really the future?" New topic

Is J# really the future?

Chris Harris
Ranch Hand

Joined: Sep 21, 2003
Posts: 231
Hi all,
There are a number of people in work trying to push J#, as a means of developing a product that will both run in Java and in .net. However J# is only runs on JRE 1.1.4, which is going to mean some big restrictions. Has any one got a better way of doing this?
Thanks for you help

Chris De Vries
Ranch Hand

Joined: Dec 05, 2002
Posts: 65
I think an interesting open source project, which is attempting to create a java virtual machine which runs under .net, is The desired result it to have a jvm compatible with jdk 1.4 which runs under microsoft.NET and mono, and has access to the microsoft .NET framework API.
I think because of J#'s limitations, and the fact that microsoft is pushing C#, that J# will not end up being widely used... of course I have been wrong before and could be wrong again.
Chris Harris
Ranch Hand

Joined: Sep 21, 2003
Posts: 231
HI Chris,
It looks to me that J# is a nice theory but in reality the whole idea of one platform any language is far off.
Nice thing to hear as a Java Developer
Daniel Puryear

Joined: Jun 02, 2002
Posts: 22
I've been doing the Java thing since '96 and have been doing the .NET thing for only 6 months. I started in C# just because I wanted to pick up the new language but then quickly reverted to J# since everything I could do in C#, I could do in J#. I have ported a serious JDK 1.1.4 charting application to the .NET with VERY little difficulty. I've also played with the new J# supplement that picks up many of the Swing components and the new .util classes in prep for another port to the customers .NET environment.
That having been said, I don't think anyone should be confused about the role of J#. J# is intented to help migrate the PROGRAMMERS to the .NET, not the applications. It should not be the basis on which to formulate a decision about how best to develop and support cross-platform applications.
For a Windows environment, .NET has much to offer in terms of performance and programmer convenience and it will be around for a VERY long time. Since J# has always had the design interface into the Windows Forms; us Java GUI programmers will slowly migrate to the Forms designer as we get more comfortable with the forms. (Windows GUI components have always had a richer event model than the Swing) You can (I have) mix and match J# and C# classes freely - I have not had any serious inter-op problems yet. For serious low level Windows interface coding, I'd switch to C#.
Just some thoughts as I read your post ---
- Dan
I agree. Here's the link:
subject: Is J# really the future?
It's not a secret anymore!