Friday, September 5, 2008

J#: Java on .NET

Today, I did a presentation on J#, at the September 2008 meeting of the Microsoft Student Champ community at the Microsoft Sri Lanka office, in Nawam Mawatha, Colombo 02. I decided to add here a few important aspects I discussed at today's meeting.

Taking a brief look into how various lrogramming langauges evolved, C/C++ strongholds of the 80s and early 90s, has by now gradually been reduced to a underlying system of core functionality that supports highlevel managed frameworks that sit upon them. Java was the most popular such managed runtime based programming language that came into being in the mid 90s.

Understanding the potential, and the possible gains in market and the ability to fortify the Microsoft Windows based production front, Microsoft put forward two main strategies, which involved the creation of an MS version of Java, which became known as J++ and the better replacement to Java, known as C#. VB.NET grew to become C#'s cousin but with some of the obviously crappy logic that makes programming a nightmare at times.

Due to some reason in time, Sun began to start accusing Microsoft for its unlawful use of Java technology that was to a great extent propietary in ownership, which lead to the demise of J++, which was brought to a virtual standstill in 2001. J# was then thought of, which became a combination of Java and C# which is capable of plugging most Java code written before and around 2001, at the time when J++ was officially discontinued. Mostly developed in India, J# became popular with it's integration to Visual Studio 2005.

J#, began a journey in which Microsoft provided a mechanism to make use of its investment and time, in making Java from MS a reality. Today, J# which was last released in mid 2007, has started a process of gradual decommission, and by now the project has been discontinued, and marked as will be supported only until 2015.

In spite of its current stance, J# provides an excellent way in which legacy Java applications can be integrated into .NET environments, which would be quite advantageous if you are planning to do 0% work in moving your bulky legacy Java code base into a modern .NET base.

To be continued...

No comments: