ONJava.com -- The Independent Source for Enterprise Java
oreilly.comSafari Books Online.Conferences.

advertisement

AddThis Social Bookmark Button
Article:
  What .NET Got Right
Subject:   .NET will take a Bigger Bite - 2
Date:   2002-02-13 06:55:06
From:   kjambu
Response to: .NET is not available clientside, nor is it portable serverside.

With SOAP, XML and WebServices going to be the future of Distributed computing, according to me the issue of Serverside portability is a non issue. Even talking about Java's portability, how often can one deploy a EJB developed in Weblogic in WebSphere or vice versa without tweaking around nitty gritty things. This I am assuming both the servers are running on NT. If it is on two different Operating Systems you know what are the issues. Many things in Java are still vendor dependent and each Application and WebServer has its own extended features. Then what are we talking about server side portability. If JVM is what is serverside portability developing a MVM (Microsoft Virtual Machine) should be a jiffy.


Thanks for accepting that client side java is dead. Microsoft's innovative client side tools help enhance the RAD environment even better. Take for instance, i need not even worry about browser compatibility issues, that too without writing a single line of code.


What are we talking about Cross platforms. How many of us have used Java to develop pure Cross platform applications. If that is the case why even after 7 years of Java, JNI is around. How many of us have written Java applications to access Visual Basic DLLs.


Even today i can say, to be on the safe side, more than 70% of Java programmers use notepad or some such editor to write Java programs. Many of the Java presentations are done in Microsoft Powerpoint. The first or early versions of the JDK and other packages come for Windows.


For reliability purposes, it is better to be with a single vendor, rather than no vendor at all. Howmany of the mid level organisations have the technical expertise to play around with the Linux Operating System, Apache Open Source Servers and so on. That may be good for research not for business.


And let us not tie up this discussion with the current state of the internet. It is only at an infant stage. Making a Language or technology work across Operating Environments should not give us the last laugh. That too, at its best, is a patch up solution only. We do not know what the Operating System of tomorrow will look like. None of the Operating Systems that we are using today, including Unix, Windows and the Mac were built for the internet era.


Newer things will emerge. New Operating Systems have to be built and there is a long way to go. I feel by the end of this century, humans will forget that they have to go to a shop to buy things. An analogy to that today for example is, when a mother asks her kid as to from where does milk come, the kid says gleefully, 'From the Fridge'. (Not from the cow anymore!).


According to me .NET is the third solution for the internet. First was ASP and COM, then Java and now .NET Let us accept facts and embrace the better technology. There is nothing like monopoly. When something better comes up no one can dictate. All of us know that Java definitely cast a shadow on Microsoft technologies. Then why this fear syndrome of monopoly. Is Unix dead? Let us see what is good for humanity. Let us take the best of both worlds and get going.


I am a Java fanatic... But, Because it was good, we cannot leave the better things that are coming up and lag behind.


Let us face reality. Let Sun and others bring something better as the fourth solution, probably by 2005 when we have faced some more problems in internet commerce. For instance, can we look at a solution for eliminating the stateless nature of the protocols now. The world will see more of Ritchies and Goslings and Andreesens.


I wonder how many Bill Gates' the world will see.


Kudos to Bill Gates and his team. Today is 13th of February 2002 the launch day of VS.NET and i am happy that i got the opportunity to write this piece. My lanuage may be harsh but no hard feelings intended.


Thanks
Jambu Krishnamurthy