Linked by Eugenia Loli on Mon 19th Sep 2005 17:02 UTC, submitted by Eli M. Dow
Mono Project Build applications for Linux while maintaining cross-platform capabilities using .NET languages.
Thread beginning with comment 33945
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Costs of Mono
by on Tue 20th Sep 2005 12:38 UTC in reply to "Costs of Mono"

Member since:

It also possible if you use Java. The java is free at this moment but I can't see any warranty for the future. Yes, the gcj always will remain free, but if SUN (or any successor) sue the gcj developers or users the free state of java can be changed.

But it is the smallest problem. The bigger is the power of .NET. M$ have enought money and interest to develop .NET. IMHO the future is the .NET, and the costs of refusing .NET/mono can be very-very hight.

Reply Parent Score: 0

RE[2]: Costs of Mono
by on Tue 20th Sep 2005 13:03 in reply to "RE: Costs of Mono"
Member since:

Java is under a RAND grant. Anyone is free to implement a java environment with no strings attached, other then that sun reserves the right to what is called "Java", and what isnt. If Sun could start sueing IBM for Jikes asap (sun and ibm have been in even more of a tug of war match over then then sun and microsoft)

As for ignoring .net, we arent talking about that, we are talking about adopting it. .Net is extremely new, and in the world of APIs new is generally not a good thing. It means it has some nifty new features that java does not, but java has a collosal head start in many areas. it will take microsoft years to get .net up to the same level as the java api for one. another thing to consider is that java is virtually synonmous with "enterprise computing", if your making an enterprise webapp, chances are you will be using j2ee/oracle/*nix not .net/sqlserver/win2k3. the reason for this is that java has proven itself to be both secure and robust. Many desktop users dont realise how insanely popular the platform is in the business world, because they dont see many desktop apps (this is because of the swing issues i mentioned earlier)

Last but not least, there are (currently) more people working with java for their day to day jobs then any other language. It would be a nice bonus to use a language that is the majority of programmers bread and butter, it would mean the barrier to entry for writing gnome apps is next to nothing. it would be a big change from C, which has been on a steady decline for decades now (its not even taught in many courses anymore). Java would definately be the best choice at this point in time for getting young blood into gnome (to be fair, .net probably will be second best within the next few years, and if history has taught us anything, take the lead)

Reply Parent Score: 0

RE[3]: Costs of Mono
by on Tue 20th Sep 2005 13:42 in reply to "RE[2]: Costs of Mono"
Member since:

.Net is extremely new, and in the world of APIs new is generally not a good thing
It is true, but IMHO the .NET will successor of java. The C# and java language, basic class libs are very similar. But the designers of java created many wrong decisions when java was born: no properties, no operator overloading, no databinding, AWT, etc. And some of this early decisions can't change without break the compatibility.

because they dont see many desktop apps (this is because of the swing issues i mentioned earlier)
Not only the swing. IMHO a biggest problem is a virtual machine. The .NET (and Mono) uses only one VM for every desktop applications. But every desktop java apps are uses their own runtime environment. The java 1.5 promised change, but now, after 1 years of 1.5 the most of java apps are use separated JVM.

And the biggest problem of desktop java is the future. IMHO if .NET will strong enought the running of desktop java apps will be uneasy on windows. And the 95% of desktop market is windows based. And IMHO in the near future the .NET will replace the flash on the client side. In this case the linux desktops without .NET support will dead.

if your making an enterprise webapp, chances are you will be using j2ee/oracle/*nix not .net/sqlserver/win2k3
At this moment. But IMHO it will change in the near future.


Last but not least, there are (currently) more people working with java for their day to day jobs then any other language.
It is true, but if you count the potential .NET developers you must count every Visual Basic, Delphi, (or maybe java :-)) and other programmers, not only the C# developers.

Reply Parent Score: 0