Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
If I were to begin writing an application using Java with the intention of porting it to other platforms with little or no modification, would it be wise to consider using the .Net framework instead?
I have no specific targets in mind with respect to platform. At a minimum, Windows/Mac/Linux support would be nice. Also ease-of-use for the end-user is a consideration.
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
I wouldn't go with .Net. Mono is not bad, but if you use some obscure corner of C# or the .Net library that Mono does not support, then you're screwed. This is way less likely to happen in Java because Sun stands behind full runtime implementations of Java for Windows, Mac and Linux.
For cross-platform compatibility .net is not the answer... and don't give me any "but mono..." nonsense. Mono's just isn't up-to-date w/ current framework class libs.
I think, if you care about native look-and-feel in Mac environment, you may go for mono with keeping the UI and the core loosely coupled. Because in mono you can achieve more native look-and-feel for different platforms using different mono based UI APIs like Cocoa#. But you have to spend more time.
May be Java also supports the APIs for different platforms. But the practice is not common I guess.
Another point is, if using C# makes you more productive, go for mono.
In Microsoft's words, the .Net Framework consists of the following parts:
* Common Language Runtime or CLR, which provides an abstraction layer over the operating system
* Base Class Libraries, which are pre-built code for common low-level programming tasks
* Development frameworks and technologies, which are reusable, customizable solutions for larger programming tasks
Mono is a software platform designed to allow developers to easily create cross platform applications. Sponsored by Novell (http://www.novell.com/), Mono is an open source implementation of Microsoft's .NET Framework based on the ECMA standards for C# and the Common Language Runtime.
It provides decent support for the CLR but it is lacking the breadth of "Base Class Libraries" and "Development frameworks & technologies". That is especially true if one considers the enormous ecosystem of Java. The latter has achieved a level of maturity and is supported by a plethora of publications (Wikis, User Guides, Books, Articles, etc.). Lastly, there has been a number of new languages (e.g. Groovy, Scala) and frameworks (e.g. Grails, Spring Roo, GWT) that can make your team enormously productive in a wide area of functional domains.
The only caveat would be, of course, if you must integrate Microsoft products (e.g. Microsoft Office) in your application (whether within the browser or a stand-alone app). In that case the .NET approach would give you a significant advantage but it would not be easy to carry over these advantages to other platforms (e.g. Linux).
The Java ecosystem is enormous and contains high-quality libraries for pretty much anything that you can think of. In fact, before you start writing your app., you should conduct a search across the Open Source projects that have been written in Java. It is very likely that what you are trying to build is very similar to something that already exists. So, depending on the license (look for LGPL, BSD, MIT, etc.), you might find something to get you started before you even break a sweat.
In summary, if your primary goal is to achieve multi-platform support then Java is your best bet.
Obviously Java does have some multiplaftorm capabilities, where .Net/Mono is risible. You can say C is portable too, and you'd be roughly as right.
If it's desktop applications, I'd just do it in Qt. By far the best GUI framework out there, and really multiplaftorm.
For non-desktop, a good scripting language is usually the way to go.
Definitely go with Java over .NET if cross-platform is your main concern.
.NET basically locks you into the Microsoft technology stack. Mono is nice and all that, but it isn't comprehensive or up to date with all the .NET libraries (and probably never will be given they are chasing a moving target and Microsoft has no real incentive to help them...)
On the other hand, I wrote a reasonably complex (including Swing GUI) app in Java and successfully ran it first time on both a Mac and Linux, with no need for even a recompile. In that respect, Java is about as cross-platform as you can hope for. There are a few areas where you have to be careful (e.g. using JNI to access native libraries) but if you stick to standard, pure Java then portability is pretty much perfect.
Also see this post I made about Java as a platform choice.
I'd say go with what you like. If you - while coding - keep in mind that the app has to run on different systems and test early and often I bet you're going to be o.k.
I haven't written any java in a long time „in the early days” porting wasn't always fun either. (i.e. 3D graphics come to mind...)
If you choose mono/.net you either need use windows.forms and do all your forms in windows (there is currently no windows.forms ui-editor in linux) or you could use gtk and have your windows-users install gtk first.
I personally have (in 2 projects now) doubled the ui. Wpf for Windows, gtk for the rest...
Path.Combine() instead of adding / or \ ) it will work out
– Nils
Dec 28 '10 at 15:22
Just Create a web application and be done with it.
Having developed both desktop applications and web applications.
I have come to the conclusion that the majority of desktop application work just as well as web application. With the rise of RIA technologies such as Silverlight, the gap has narrowed even further.
Please note, I'm not advocating all desktop applications here, in some cases a full FAT client will be needed.
