This article assist developers of .NET, Windows client/server, and ASP applications make the jump to the Java platform. It provides a high-level guide for .NET developers who want to migrate their e-business applications to J2EE or build J2EE applications from the ground up.
Leverage your .NET smarts to build J2EE apps
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
after all the articles on jumping from java to dotnet (even from java developer magazine) I was waiting for somebody with the balls to pen an article about the reverse.
I write this from the POV of somebody who likes both platforms, but wants to see lots of competition to keep both scared and innovative.
I think this is also good for people who want to expand/create there apps to run on more then just Windows boxes. .NET has no way of doing this yet so this is a door way to allow that.
ASP.NET is feature complete on Mono.
Question to Java-devs who also happen to know C#:
Do you find any technical reasons why a C# developer would switch to java? Are there any technical advantages Java has over .NET/C# ?
I’ve read the IBM document and it looks like the only reasons they mention are political. In every other aspect they either mention: “java has it too”, or “java doesn’t have it, but it’s possible to live without it”.
Anybody notice that the .Net code in this article contained a ton of errors. Also some of the information is misleading. Such as when they were comparing Java to Visual Basic for the intigers. Then said Long is VB.Net is a 32-bit signed intiger. Which is totally wrong it is a 64-bit signed intiger. And why is this the only place they referenced VB.Net and the whole article is in C#.
This just looks like IBM is feeling the presure of .Net and is starting to spread FUD.
Forget the thing about VB.Net that I just stated, but I still feel that this is just a political artilce. Plus who is going to convert from VB to Java, I could see C# to java.
I believe the biggest reason to swich from .NET to a Java platform would be the fact that you can run Java on more hardware and with more operating systems, whereas .NET seems to be a MS Windows Only thing. If your entire environment was Windows and nothing else, I guess this would be fine for you, but many places run a mix of Un*x, Linux, xBSD and Windows, so a Java program environment would most likely fit better than the Windows Only .NET option.
** I know the MONO project is working on making .NET more portable to other operating systems, but I don’t know the status/completeness of this project…
** I know the MONO project is working on making .NET more portable to other operating systems, but I don’t know the status/completeness of this project…
MonoDevelop, a GTK# port of SharpDevelop, runs under Mono, Linux.
Given that its pretty damn complex, I’d say that Mono is doing very, very well. ASP.NET feature complete, too, to boot.
“Do you find any technical reasons why a C# developer would switch to java? Are there any technical advantages Java has over .NET/C# ? ”
NONE. In fact Java the language has a few mind bloggling shortcomings. For instance you can’t pass a value type by reference (you have to put it into an array !!). Also it doesn’t have structs, operator overloading and their implementation of generics(in java 1.5) is pure crap
The article is pure FUD.
** NONE **
Clearly from someone who has limited experience (if any) in both languages. I consider C# to have some very nice features that a C/C++ programmer would expect to find that are not in Java, but to say there are no advantages is a short sighted statement made by someone with little to no software engineering experience. But whether you should use Java or C# depends on what you end-game is; Windows UIs, total WIndows solution, C# and the .NET framework should be your first consideration. Mixed platforms, scalable enterprise server applications, then maybe you should consider Java over C#.
Both langauages and their associated frameworks are just tools. Pick the one that you can build the best/fastest/cheapest/on schdule with, and you’ve picked the right one for you.
Common mates, this pure bollocks! Jave is inferior to C# in every aspect, ASP.NET is way easier and nicer to use that JSP. .NET is what the java platform should have been. Sun doesn’t give a rat’s arse about java. The developers have been asking since 97 for generics and other features, the only resaon they have added some of that stuff to 1.5 is because of C#. And generics in java are pure shite. You still box it to object and unbox it, the compiler adds type casting for you. In .NEt genrics are real.
…and the world is flat, and the sun revolves around the earth, please get a clue and become a real developer. Your statements above prove you don’t even know what .NET is in the grand scheme of a software solution/architecture. You really need to study some compiler theory and the history of HLPL. You’ll realize that each language owes many of it strengths based on the weaknesses of its predecessor. Why did MS need C#, (and more precisley need it to look and behave very much like java)? It wanted to leverage the skill set of the existing java developers; it didn’t do it to make the VBers and VisualC++ guy happy. Why is MS creating X#/Xen…because of the weaknesses that C# has in processing XML. Each language is a stepping stone to the next…just wait for Fortran-77 — 2077 that is….then we’ll have a superior language