|
how much code does it take to call yourself a j# developer? if it's two lines then give me ten minutes and i'll update my CV.. .
|
|
|
|
|
Now that we have Mono around for Linux, I'm surprised Java is still alive because it is so much slower than .NET and Mono. J# was created to simply give the Java programmers an easy path to migrate to .NET. The extremely poor performance of Java has always been its weakness, and I have never seen a solid way to overcome it.
Daniel Petersen
|
|
|
|
|
Daniel Petersen wrote: and I have never seen a solid way to overcome it.
ANSI C++. 
Jeremy Falcon
|
|
|
|
|
I totally agree that C++ is the best language to build high performance applications, but I was referring to there not being a solid way to overcome the problem within Java itself.
Daniel Petersen
|
|
|
|
|
Daniel Petersen wrote: I'm surprised Java is still alive because it is so much slower than .NET and Mono
In my experience, Java is pretty much as slow fast as .NET, and less slow faster than Mono.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
I'd have to agree. I think the slowest thing about Java could be the UI libs, but for console apps it's not bad. Although, I still hate Java, I'm just trying to be fair. But, JSP is a steaming pile of crap though.
Jeremy Falcon
|
|
|
|
|
I tend to disagree with your assesment (if I am decoding it correctly...). I believe that Java is not near as fast as .NET and in my opinion (at least running MONO in the WIN32 environment) MONO is faster than .NET... Please don't flame me for that statement people... I meant no harm by it...
|
|
|
|
|
I definately agree with you. In my experience .NET tends to do the same job as a Java application in half the time, utilizing half the resources. This is using the same design and UI elements for both. Another key advantage of .NET is in deployment of web applications. ASP.NET is simply copy/paste deployment, whereas Java requires a multi-step process. With ASP.NET you just need IIS but Java web apps require Apache + Tomcat and if you do even the slightest thing wrong in deploying with Tomcat the whole thing blows up. I experienced this first hand with DSpace which is a fairly complex application, and the hardest part of the installation was just getting it to deploy within Tomcat properly. In all fairness, Mono does require XSP to run ASP.NET, but it's deployment scenario is not nearly as complex as Tomcat.
Daniel Petersen
|
|
|
|
|
Daniel Petersen wrote: The extremely poor performance of Java has always been its weakness, and I have never seen a solid way to overcome it.
I have a friend with over 20 years' experience who would dispute this.
http://www.cutthecrap.biz/[^]
However, I've not attempted to verify his claims - much to his amusement, as he finds he gets virtually zero interest even from other Java developers (I'm not a java developer).
Nonetheless, I know that he does not bullshit about this kind of thing. I imagine he gets the performance by superior design.
Kevin
|
|
|
|
|
Even though I have never done any professtional work on JAVA but I donot agree that performance of JAVA is less than .NET. I think if JAVA is not faster than .NET then it is also not slower than .NET.
This is a good point that C++ is the language of choice for high performance application.
C++ ever facinating language 
But lets back to J# if it is there to attract Java developers then what extra J# is giving in J# that is not present in Java?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
