eweek.com— Microsoft declares Java dead and now focusing on different systems to compete with other platforms like Ruby on Rails.
Jul 28, 2006View in Crawl 4
Georgia Tech also validates this claim.Within the past year Georgia Tech has switched one of its main CS classes, CS2335: Software Practicum, from Java to MS .Net. This may not seem like a big deal; however, it is definitely a sign here that Java is losing influence, especially in education.
With more and more software moving away from Desktops and into Web Browsers, I think it's rather foolish to proclaim a top server-side technology "dead."
"Microsoft is leaving Java in the dust, but the company still has room to grow in the developer arena, a key executive said."Riiight, buddy. Java is alive and well, don't worry. I use it to build scalable systems that handles millions of hits, I know of plenty of other systems using Java. I don't know about .NET, so I won't knock it, but don't freakin' lie. Java is here to stay.
This is absolutely inaccurate. I am a Director of a company and we use Java and Apache and it's not because they're free. I've been bitten in the ass so many times by closed systems that I will NEVER subject my business critical systems to it ever again. It's just not worth it. The amount of times I've had web applications or other proprietary code freak out because of a database update or some other minor issue that we can't fix because we can't see the code has taught me a number of very hard and expensive lessons, I own the company so time IS money to me. 1 day waiting for a vendor to acknowledge a problem, then x days to fix it (if they decided to) vs 1/2 day fixing a problem or less in the case of our latest issue with a database update causing problems with a single query in the application.. the math is very easy. The fact that they're free is just the icing on the cake.
Yeah.Muglia said that .NET was beating J2EE.The article - in fact, its title - said that .NET was beating [all] Java.J2EE is one of many collections of packages that Java developers can select from to create web applications. Even enterprise applications. They do not have to use any version of J2EE.On top of that, J2EE is "last year's" enterprise edition of Java. Java 5 EE came out late last year or early this year - depending on whether you are talking spec or implementation.So, by fixating on the old version of Java EE, it makes it look like Java use is falling of, when in fact the opposite is happening - companies are upgrading to the current version of Java EE from the old version of Java EE.So the article contained a number of inaccuracies. The inaccuracies were nicely summed up by its title, which is an incorrect statement. That is why people have been marking it as inaccurate, most likely.As people have pointed out, the published lists of language popularity put the .NET languages pretty far down the list - behind Java, C, and a number of other languages.The other languages, that outrank the .NET ones happen to be cross-platform in terms of O.S. - and in terms of CPU. They run on PowerPC, X86, Unix/RISC processors from IBM, Linux, Sun Unix/RISC SPARC processors, MS-Windows, Mac OS X - and that is just Java. C is everywhere on everything - its like a prion, practically.The .NET languages are nowhere near that portable - quite the opposite. To use them you have to:1. Develop compile/run/test on MS-Windows.2. Ship product to run on MS-Windows.3. Buy developer tools from Microsoft.4. Only develop and target Intel x86 (or binary compatible) CPUs.Those are not fatal flaws. Some people are biting the vendor-lockin, OS-lockin, CPU-lockin bullet and going for it.Others do not have to because they are not even running on the desktop but on a web server or UI-less server. Or, they can do all the GUI stuff they want with Swing.The things on that list above are some really extreme limitations. Look at how much of the total CPU pie chart, total OS pie chart, and total computer system pie chart you have to cut away and throw out to embrace, say, C# or VB.NET.On top of that, you have compatibility. Java managed to preserve most of the compatibility If you do want to zero in on one .NET language, like Microsoft to some degree and the author to a large degree, zeroed in on .NET - focus in on J#. It is really just Sun Java 1.1.5 language reshaped to be incompatible with the far more advanced Java 5 (i.e. JDK 1.2 - 1.5).There is no way that J# is as popular as "Java". But I could use that same argument to make a resoundingly successful case that .NET was dead and Java had won the language wars, along with just about every other language, maybe even LISP.Anyway, not only do the widely available, published stats indicate that the title/assertions of the article are wrong. Just a little common sense and intuition highlights how unlikely the article is from being true.
awgneoJul 28, 2006
Georgia Tech also validates this claim.Within the past year Georgia Tech has switched one of its main CS classes, CS2335: Software Practicum, from Java to MS .Net. This may not seem like a big deal; however, it is definitely a sign here that Java is losing influence, especially in education.
bpapaJul 28, 2006
With more and more software moving away from Desktops and into Web Browsers, I think it's rather foolish to proclaim a top server-side technology "dead."
geronimoJul 28, 2006
"Microsoft is leaving Java in the dust, but the company still has room to grow in the developer arena, a key executive said."Riiight, buddy. Java is alive and well, don't worry. I use it to build scalable systems that handles millions of hits, I know of plenty of other systems using Java. I don't know about .NET, so I won't knock it, but don't freakin' lie. Java is here to stay.
jeffyjonesJul 28, 2006
Nice. Look out for the black helicopters. :rolls eyes:
williamdyerJul 29, 2006
Paint.NETTry it. It's useful for when you don't want to twist your melon about the Gimp's UI.
myrmJul 29, 2006
This is absolutely inaccurate. I am a Director of a company and we use Java and Apache and it's not because they're free. I've been bitten in the ass so many times by closed systems that I will NEVER subject my business critical systems to it ever again. It's just not worth it. The amount of times I've had web applications or other proprietary code freak out because of a database update or some other minor issue that we can't fix because we can't see the code has taught me a number of very hard and expensive lessons, I own the company so time IS money to me. 1 day waiting for a vendor to acknowledge a problem, then x days to fix it (if they decided to) vs 1/2 day fixing a problem or less in the case of our latest issue with a database update causing problems with a single query in the application.. the math is very easy. The fact that they're free is just the icing on the cake.
whiskerthemadJul 29, 2006
I hate Java. I hate .Net.I've just had longer to hate Java, so I'm better at it.
jilaganJul 30, 2006
this is a joke, right?
johnnysoftwareJul 31, 2006
Yeah.Muglia said that .NET was beating J2EE.The article - in fact, its title - said that .NET was beating [all] Java.J2EE is one of many collections of packages that Java developers can select from to create web applications. Even enterprise applications. They do not have to use any version of J2EE.On top of that, J2EE is "last year's" enterprise edition of Java. Java 5 EE came out late last year or early this year - depending on whether you are talking spec or implementation.So, by fixating on the old version of Java EE, it makes it look like Java use is falling of, when in fact the opposite is happening - companies are upgrading to the current version of Java EE from the old version of Java EE.So the article contained a number of inaccuracies. The inaccuracies were nicely summed up by its title, which is an incorrect statement. That is why people have been marking it as inaccurate, most likely.As people have pointed out, the published lists of language popularity put the .NET languages pretty far down the list - behind Java, C, and a number of other languages.The other languages, that outrank the .NET ones happen to be cross-platform in terms of O.S. - and in terms of CPU. They run on PowerPC, X86, Unix/RISC processors from IBM, Linux, Sun Unix/RISC SPARC processors, MS-Windows, Mac OS X - and that is just Java. C is everywhere on everything - its like a prion, practically.The .NET languages are nowhere near that portable - quite the opposite. To use them you have to:1. Develop compile/run/test on MS-Windows.2. Ship product to run on MS-Windows.3. Buy developer tools from Microsoft.4. Only develop and target Intel x86 (or binary compatible) CPUs.Those are not fatal flaws. Some people are biting the vendor-lockin, OS-lockin, CPU-lockin bullet and going for it.Others do not have to because they are not even running on the desktop but on a web server or UI-less server. Or, they can do all the GUI stuff they want with Swing.The things on that list above are some really extreme limitations. Look at how much of the total CPU pie chart, total OS pie chart, and total computer system pie chart you have to cut away and throw out to embrace, say, C# or VB.NET.On top of that, you have compatibility. Java managed to preserve most of the compatibility If you do want to zero in on one .NET language, like Microsoft to some degree and the author to a large degree, zeroed in on .NET - focus in on J#. It is really just Sun Java 1.1.5 language reshaped to be incompatible with the far more advanced Java 5 (i.e. JDK 1.2 - 1.5).There is no way that J# is as popular as "Java". But I could use that same argument to make a resoundingly successful case that .NET was dead and Java had won the language wars, along with just about every other language, maybe even LISP.Anyway, not only do the widely available, published stats indicate that the title/assertions of the article are wrong. Just a little common sense and intuition highlights how unlikely the article is from being true.
wistarAug 1, 2006
Some reading from a very good writer, Joel Spolsky:<a class="user" href="http://www.joelonsoftware.com/articles/ThePerilsofJavaSchools.html">http://www.joelonsoftware.com/articles/ThePerilsofJavaSchools.html</a><a class="user" href="http://www.joelonsoftware.com/items/2006/08/01.html">http://www.joelonsoftware.com/items/2006/08/01.html</a>And a commentary by Steve Yegge on Java:<a class="user" href="http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html">http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html</a>
thesakSep 27, 2006
Does that show ongoing projects and actual paying jobs using each of the platforms, or just searches people are performing on Google?