> From: [email protected] [mailto:discuss- > [email protected]] On Behalf Of Yves Dorfsman > > For > .net apps, you can only install them on MS Windows machine, while a Java > apps > can be installed anywhere the full JVM (graphical) can be run.
This is again, mostly untrue. Let's put it this way: You develop a java app, and you only test it on one platform. Your user comes along with a different platform and tries to launch it. Guess what's going to happen? Most likely it won't work. But if the developer spends a tiny incremental amount of time testing on the other platform, then it's mostly reusable code with just some idiosyncratic tweak to make it cross-platform compatible. Same is true with .Net. I find, as I sit here day after day, coding .Net, I develop on .Net and debug on .Net. And when it works, then I click on Debug in OSX or Linux. Visual Studio reaches out to the machines where I've installed the linux or mac remote debugger, and it executes the code remotely, and invariably, it doesn't work on the first try. But after a trivial tweak, it all works cross-platform. In this regard, Java == .Net In fact, Java == .Net so amazingly across the board, that to me, the most significant factor in choosing java vs .Net is how well you like the process of applying regular updates, and how well you like the IDE. Of course, sometimes there will be a prevailing factor - if you're coding a windows-only application, then .Net is the winner. But aside from that ... Heck, Xamarin's (the developer of mono) new business model is to sell .Net compatibility to Android and iOS. So even the argument of "use java on android" isn't completely accurate. But I'm guessing, the statement "use java on android" is equally true as the statement "use .Net on windows." _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
