The Artima Developer Community
Sponsored Link

.NET Buzz Forum
.NET versus J2EE Complexity

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Randy Holloway

Posts: 443
Nickname: randyh
Registered: Aug, 2003

Randy Holloway is a developer and writer focused on enterprise software.
.NET versus J2EE Complexity Posted: Dec 16, 2003 8:20 PM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Randy Holloway.
Original Post: .NET versus J2EE Complexity
Feed Title: Randy Holloway's Weblog
Feed URL: /msdnerror.htm?aspxerrorpath=/rholloway/rss.aspx
Feed Description: Commentary on Yukon, the CLR, and related technologies interspersed with personal opinion.
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Randy Holloway
Latest Posts From Randy Holloway's Weblog

Advertisement

Having compared notes with some architects that have worked on both platforms and having consulted with some people on some fairly complex application requirements where J2EE and .NET were both being considered, I would tend to agree that J2EE is "more complex" than .NET, as stated by Microsoft employee Frank Arrigo in this iTNews article.  From my perspective, this complexity is driven by the application server story for J2EE, a problem that doesn't manifest itself with .NET on Windows servers.  I'd be curious to hear from architects that are working with both platforms to get their perspective.

Read: .NET versus J2EE Complexity

Topic: SharePoint Resource Kit, Windows Sharepoint Services Search, Host Integration Server 2004 Previous Topic   Next Topic Topic: Saddam Hussein Captured

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use