I disagree. C# and Java is very different. Syntax maybe the same but once u start program it u will know its different. Is your comment based on your experience or other ppls experience ? Do you know C# and Java?
Yes I know Java. I've been trained by Sun to use the language. From my understanding C# is MS's own attempt at a Java-like language ("C++-- blah blah blah..."). MS has critisised the idea of Java, yet ironically enough they're developing C# after the court case and taking WFC concepts with them. Obviously since C# has the abilities of Java it becomes a problem for Java, especially if C# is supposed to be better. As my Java trainer had said when he was reading about C#, he "wanted to know the enemy".
Again i disagree. Sun does not have things like MyServices. Sun had web services.. not myservices. My services is colelction of webservices ms willbe providing. eg passport (global auth system), myalerts. .NET. Web service is a method of making a object or classes invokable (???) remotely whether its thru SOAP/XML or Binary (remoting). Waht interoperatbility? .NEt doesn't offer interoperability with anything except COM and COM+. It can't even run on win98!!!
You are thinking of RMI. I'm talking about the NC concept introduced by Oracle sometime in the 1990s. Sun definitely has something similar to HailStorm even though the NC concept has died. The things that ONE/iPlanet are supposed to offer like WebTop are to ultimately provide a set of services like my[insert some word here], just maybe without anything shoved down your throat. And obviously the idea of the O in ONE means interoperability between packages that use open standards.
Passport = ONE Identity
myServices = ONE Directory
myInbox = ONE Messaging
myCalender = ONE Calender
From what I see, HailStorm goes for the end user using XML and .NET, ONE goes for web enabled devices using XML and Java. Since web services based heavily on XML, the .NET framework can easily interface with existing information storages - that is how I see it's interoperability.
Java is not slow. Java maybe slow on windows but Java is incredibly fast in unix and linux. You will probably have oracle on the backend for java apps and java provides native connection classes which allows perf comparable to .NET/sql server
I agree that Java is good for backend services, its proven and robust in that sense. What about mainstream applications that end users are actually interested in? AWT is simply too slow and sluggish compared to WFC, not to mention that many screen elements are plain missing because it was designed to run across platforms. We were using UltraSPARC boxes running SunOS at the Sun training center, and even on a box like that its speed was definitely far from a native application.
disagree again. Do you mean Unix and Linux is going to die as well ? Beside from C++ , Java is only (decent) compiled language on these platforms. PHP, Python. they are all script languages.
Unix, Linux and Java were never related anywhere, so I don't mean *nix are going to die, I never mentioned it anywhere. *nix have a well settled user base, OS/2 didn't. Now *nix its moving towards the mainstream because its getting easier to use, OS/2 only did it to an extent. There is competition for Java out there now, just like OS/2 had NT against it, and I feel that Java's disadvantages does not outweight its advantages (in most cases), so I think there is a chance that it might eventually die out, but maybe over a long long period of time. But there is no mainstream competition with *nix. And that, is my 2 cents.