
July 24th, 2003, 11:52 AM
|
|
Junior Member
|
|
Join Date: Jul 2003
Posts: 1
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
Quote: Originally posted by netytan
Ah, I think i'll stick to Java then. A, because of as you mentioned its ported to ever platform and B, simply because it seems to be alot more desirable on the job front .
Thanks a lot for your help, easy to understand and got the point accross.
Ta,
Mark. |
Speaking strictly from experience, I've been doing Java for 3 years and recently started doing .NET [have previous exp with ASP]
The problem with Java is the huge dependencies on third party code [usually opensource]. These opensource projects are frequently in beta or some chaotic state that causes constant changes in your own code to keep up. I actually started doing jsp / servlets for this reason [asp was too limiting]. I used J2EE, Jboss, Tomcat, log4j, struts, jetspeed, etc etc etc. It just came to a point where 40 percent of my time was spent keeping up with someone else's bugs.
The cross platform mantra of Java is really not that relevant. Simply put, you will get more done in shorter time in .NET, boiling down to cost savings for your client/company. Anyone who selects a platform just because its "cross platform" is indeed lying to themselves because when you say cross platform, most likely you have already made the decision to deploy on unix and only unix, so whats the point in being "cross platform".
Dont get me wrong, I like java. But I like .NET better
Regards,
Mark
|