Thu, Jun 23 2005 9:54 AM
There’s More to Java vs. .NET Than Technology
A new colleague of mine, Raynni Jourdain (LogicaCMG, Arnhem), pointed me towards this article about Java vs. .NET.
In short, it says .NET for projects that have ease-of-use, need quick time to market and a lifespan of 2-5 years and Java for more complex projects, scalability and a lifespan of 5-10 years.
I'm not a Java expert, but I think I disagree...
Why couldn't you build complex projects with .NET? I think you can...!
When it comes to .NET vs Java, the words of an classic Irving Berlin song come to mind:
“Anything you can do, I can do better
I can do any thing better than you...“
With .NET, you can build reliable, fast, complex solutions, just as well (in fact, even better, because of the better tools available) as with Java/J2EE.
I see one problem, however....
A lot of times, MS (Microsoft) technology is used to rush to get results fast. And MS technology gives this ability.
MS projects are quicker to market but (because of the rush) sometimes suffer some quality issues.
On the other hand, when using Java/J2EE, it is accepted that development takes longer because it's more 'complex'...
And so it becomes a selffullfilling prophecy (try typing that without a typo ;-)) that Java is more robust...
If managers and business would deal with MS projects the same as with Java projects (time and budget), the MS consultants would get the chance to prove MS technology is ready for complex, enterprise-level solutions.
What do you think?
Filed under: .NET related, Work, Programming general