Slashdot Mirror

← Back to Stories (view on slashdot.org)

Java v. .Net?

Posted by timothy on from the yards'-worth-of-hedging dept.

JEmLAC writes: "Fawcette's running an interesting piece (in conjuction with JavaOne) on a presentation by Gartner analyst Mark Driver concerning the emerging niches for Java/J2EE and .Net in the deployment of Web services. His take is that by 2005, they will be co-standards."

2 of 39 comments (clear)

  1. Pipe Dream by cs668 · · Score: 2, Interesting

    All of this talk of web services and WSDL/SOAP repositories reminds me of how people used to talk about objects, object repositories and CORBA.

    I think it is just another big marketing load of crap. Sure WSDL/SOAP work, but so does CORBA/IIOP. The problem is it is just a pipe-dream. What are the chances that a company will have a complex service, which solves my business need, that I can just plug into. Sure they may have some simple common services - even complex ones(that will not fit meet my need). But, the integration costs will not go away.

    Sorry about ranting - I just get sick of hearing the same things repackaged as the ultimate solution every 4 years.

  2. Re:.NET not smacking Sun hard enough. Bummer by keysor · · Score: 3, Interesting
    Sun is going to have to come to their senses about this relatively soon. Resting on their laurels while MS funds a massive marketing strategy could end up crushing Java-- remember that almost everything MS is touting about .NET has already been in Java for a long time, but they're not treating it as a "better Java", but as something completely new. (Those tricky thieves...)

    The article suggests that Sun should focus on training more developers. As a student raised on Java, I think they're already in a good position here, but MS is currently on a push to get .NET taught at many of the elite universities as well. Doing some things better than Java (with a decade of hindsight) gives them an edge here...

    Now's a perfect time for Sun to reinvent Java a bit. Things like generics and the tail call optimization, for the researchers, but more importantly, a general push to the public again. Face it, there wasn't much fanfare when Java 1.4 was released. It's time to get excited about it again, is Java is going to hold out...