Java v. .Net?

JEmLAC writes: "Fawcette's running an interesting piece (in conjuction with JavaOne) on a presentation by Gartner analyst Mark Driver concerning the emerging niches for Java/J2EE and .Net in the deployment of Web services. His take is that by 2005, they will be co-standards."

Comments

Can != Should

[Tablizer]

(* For example, anyone tried printing the contents of a rich text box control? Why use a prepackage rich text box control if you have to right your own low level rtf parser to print? how furked up is that? *)

Just because you *can* use a RTF widget does not mean you should. Are you yelling at MS because they gave you the *option*? (Perhaps if they didn't give you the choice of regular HTML approaches, then you have something to fuss about.)

Choice is not evil, but the misuse of it.

Personally I think B-to-B and intranet web interfaces will disappear when a decent HTTP-friendly GUI standard finally catches on. Customers, developers, and managers *keep* asking for web apps to act like GUI's, and they don't do that very well. Web interfaces are fine for active brochures, but crappy for medium-duty business forms.

Also, is it possible/practicle to run a Python interpreter on CRL/.Net? It seems that CRL favors staticly-typed languages. I like good scriptish langs myself.

.NET is overall a good thing.

[mmusn]

Love to learn the bomb, and realize that .NET is overall actually a pretty good thing. First of all, it moves the Microsoft world away from Visual C++, and VB. This will result in Windows programmers that are used to working and thinking much more like the rest of the world. It will also result in Windows programs that are more reliable and easier to port to other platforms.

The C# language and core libraries underlying .NET are also well-documented and standardized. This means that free and third party implementations are going to happen (in fact, Mono is almost there), and a lot of free code can move more easily between the Windows and non-Windows worlds than was possible before.

And Sun needs the competition. The threat to their business from C#/.NET may finally get Sun to open up Java more. And it may get Sun to finally address some serious limitations of Java and the JVM that they have been promising to address for years but failed to do anything about.

In the long run, I think the two platforms will just merge. Runtimes will simultaneously support JVM and CLR, and Java and C# compilers will target each others runtimes.

All this is good as far as I'm concerned. I'm using Java for a lot of my work right now, but I may give Mono a try once it is fully self-hosting on Linux.

Re:.NET is overall a good thing.

[Arandir]

First of all, it moves the Microsoft world away from Visual C++, and VB.

I see you haven't been receiving the Visual .NET flier in your mail every week. I'll have to report you to the authorities.

Re:Right now...

[bigmouth_strikes]

AC, since you seem to have real life experience with .NET, it would be interesting to get more specific information.

My thoughts on your post:

1) Java runs fine on the same HW as .NET, plus you can get alot of the software for it for free. Running on Unix boxes is just a way to scale up Java, something that is not available for .NET.

2) Same for Java.

3) Performance is often better for asp, what are your specific applications and platforms ?

4) Examples ?

5) Java has this too. Nice infrastructure that is.

6) What do you mean by data access layer ? Java is excellent for data access.

7) Java too.

8) Most java tools have this too.