Slashdot Mirror
Web Services Making Software Coexist?
jgeelan writes "Despite the competitive uproar, coexistence of J2EE and .NET will be the norm and most sophisticated IT organizations will deploy on both development platforms. Who says so? No less an authority than the CTO of J2EE powerhouse BEA Systems, Scott Dietzen, writing in this month's Web Services Journal.
Dietzen acknowledges that an ongoing conflict is in progress between Java and C# and between J2EE and the .NET server family and is refeshingly honest, admitting that "there is some truth to the 'write once, test everywhere' complaint against Java."
His overall conclusion: ".NET is finding a sweet spot for programmed user interfaces, while J2EE continues to enjoy its sweet spot for server-side applications."
Unusual honesty by someone so highly placed. Isn't this just what the software industry needs more of, in these increasingly interoperable times?"
On a single platform, perhaps. It's true enough that early editions of Java's Swing weren't the swiftest UIs on the block, Swing has to contend with being platform independant. How well does a
The UI for most server-side applications is probably HTML, anyway, so I'm not sure what his point was.
That is the point. C#, ASP.NET and VS.NET are the perfect combination if you want to make HTML based UIs. You just drag a button onto a webpage, double click and write the event handling code in C#. The C# is compiled into a server side component along with some ASPX pages. The UI is completely HTML based and cross platform. The HTML generated can be transformed to work on all types of browsers (utilising the features of each). Anything that can't be done client side is done on the server side.
You pretty much write HTMl pages the same way you would write a standard GUI application and
How many months do you have to have worked with them to be considered old dog on the development team?
18? It's not like it just came out yesterday, the beta has been available for at least a year and a half. Wrox put out books on programming with the beta languages and the beta framework.
I'm afraid I don't follow you. Eclipse is an IDE. Like JBuilder or NetBeans, not an application server. Sure, you could build web applications from scratch or using a more primitive product using Eclipse or any other IDE or editor, but Eclipse doesn't replace Weblogic Server any more than emacs.
Maybe the support people don't follow you either, because you don't have a handle on what you're talking about? Maybe it seems overpriced because you're buying a web app server to do the job of an editor? Perhaps I'm being too harsh, but just some ideas.
Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
LOL :)
.NET is a framework which IS ready for primetime, because it offers all the functionality needed to build mission critical applications which have to serve thousands of users.
.NET falls short when it comes to delivering what's promised.
.NET software, I know what I'm talking about.
And why's that? WSDL isn't MS proprietry language, it's a standard defined by many companies, and should be used with UDDI, currently in v2.0.
So, f00zbll, show me the beef where
ps: I develop a lot of
Never underestimate the relief of true separation of Religion and State.
But, some of us actually want to use features not in all browsers. I don't really want to have to code separate versions of every page for Netscape 1.0 and for Lynx. You see, the world has changed since 1994. Really. It has.
Anyone who's done web pages for real has had to deal with browser compatibility. The ASP.NET approach of emitting different HTML for different browsers makes this a LOT less of a pain.