... but how exactly did it end up as a technical article in a developer's journal? Somebody put their kneepads on for that one.

My KISS solution is to hire skilled OO programmers with an experienced tech lead and then use the tools already proven. It's apparent that this "news" item slipped in when the editor was doing his/her taxes.
I agree with the others that this article is less than useless. The problem statement assumes that companies have hired inept programmers who don't know better: "It is still too easy to write code that is difficult to maintain, slow to run, and uses too much memory."
The problem is a recruiting/training problem!

Please don't fill up my mailbox with crap like that news.

It gives no usefull info except the company has released a new product. You (SYS-CON) should at least publish a link where we can read about the risks: what are they, how they appear on java projects and how to fight them. There's no need for another product promising to cure the cancer and bing world peace.

Let me restate that I agreed to recebve mail from sys-con to get INFORMATION not USELESS MARKETING

"It is still too easy to write code that is difficult to maintain, slow to run, and uses too much memory." - Dixon (self-professed or JDJ-awarded "visionary"? - what Valley spin...)

" Teamstudio's software tools specifically address Java's deficiencies." - no kidding...

It is easy to write code in any language that is difficult to meantain, slow to run and uses too much memory. Most of such code is written by not-so-good programmers. Where's the big surprise here? As long as developers need to develop too quickly, with too little time to design, implement and test properly, and infrastructure guys who still don't know how to run and tune Application Servers, we will see code that takes too much memory, is difficult to maintain, and slow to run... If everything needs to be done on the cheap and too quickly, this will continue, with whichever language might be next. Story of the proprietary software industry...

I was expecting to read the discussion. Just stating shortcomings exist does not mean anything to a programmer.

Once again we have somebody's product promo masquerading as "industry news". I guess this CTO doesn't know what an app framework is, or that there are excellent free ones like Struts that address his phony gripes.

Java is just like .Net, XML, SOAP, web services, and similar systems -- yes, it's easier to program, but it has speed, memory and maintainability problems. Check out this XML performance stuff, for example, actual *hardware* to make SOAP faster:
http://www.datapower.com

Maybe the java chip will be back

This is just self-serving marketing pablum. There is zero substance given to evaluate any of these overblown claims, and as a Delphi/Vb/C#/.Net/Java programmer, I see nothing special about Java's shortcomings.

Well, I've always thought that the Collections frame work needed help. Does your framework offer anything to ameliorate this issue?